You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As mysql protocol does not allow for parallel queries on one connection to have real parallel queries on need to acquire multiple db connections from pool. If test tries to emulate 'N queries, and each depends on previous result' than async.parallel here is unnecessary, if it's actually 'execute N independent queries' then it might be better to get a connection from pool for each sub-query
The text was updated successfully, but these errors were encountered:
The test is not attempting to emulate an "N queries, and each depend son the previous result" scenario. It it "N" independent queries." With that in mind, based on your feedback, it sounds like each of the independent queries should request a connection of its own. That makes sense to me.
The code has been modified since you submitted your issue, but I believe the raw MySQL implementation retains the behavior of using a single connection for all of the async queries. I'll raise this to the attention of those who have contributed corrections and tweaks in the node.js test code to see what they think.
As mysql protocol does not allow for parallel queries on one connection to have real parallel queries on need to acquire multiple db connections from pool. If test tries to emulate 'N queries, and each depends on previous result' than async.parallel here is unnecessary, if it's actually 'execute N independent queries' then it might be better to get a connection from pool for each sub-query
The text was updated successfully, but these errors were encountered: