3 ms·
I'm surprised there was no mention of "query planner" in the article. That would be the first thing I would check instead of assuming the driver had a bug.
by charcircuit 3y ago
I'm surprised there was no mention of "query planner" in the article. That would be the first thing I would check instead of assuming the driver had a bug.
- 101011 3y agoIf it was the query planner than I suppose the protocol wouldn't have been the way to make it fail
- charcircuit 3y agoSometimes when you think you only changed one variable during a time span, multiple variables may have changed.
- tremon 3y agoA database performance issue was ruled out earlier in the process: > Node 17 and below worked, Node 18 and above didn’t. Given that the same queries worked fine with a different client, that would point to a client issue rather than a server issue.