Some databases (MySQL for example) don't allow you to send next query before receiving result of a previous one. The only way to have queries run in parallel is have each query in separate connection. Even when query is very short it's a good idea to use connection pool to overcome network latency to DB server.
On Thursday, 27 February 2014 04:14:42 UTC+11, Reza Razavipour wrote: > > If node is single threaded and I can only be making one database call at > any time, what is the point of having a pool of db connnections? > -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
