Closed danielgindi closed 8 years ago
Well from investigating the code, I've come to the conclusion that this belongs in the knex
module, as the pool itself does not have any knowledge of specifics of the mysql
module
You got it. Thanks :)
Could be that the mysql module's api changed recently or something; I know that error handlers are bound in knex, though a similar problem to this happened at one point with postgres.
I thought that the pool is supposed to handle closed connections?.. But an app crashes periodically because of this.
And of course it is not reasonable to query for all of the open connections in the pool, and periodically send a keep alive...