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
From what I understand you don't want to mess with how LiveMysql sets up its own MySQL connections. If you're connecting to MySQL outside of LiveMysql, then just use pooling as you normally would. LiveMysql itself really does not need pooling, otherwise I'm sure the author would already be making use of that (trivially employable) feature. The reason it may not need pooling might be that it knows in advance how many connections it is going to need and that value never changes depending on load or anything else (3 connections, if I understand correctly). And so if it handles loss of connection and reconnect properly, then no pooling is necessary.
Connection pooling is something you want if you need to use connections frequently for a short period of time and then put them back. If you keep using them forever, basically, then pooling itself will provide no benefit.
What's the best way to use the node-mysql pooling functionality with LiveMysql?
The text was updated successfully, but these errors were encountered: