myndzi

Fix turned out to be somewhat easy (though still a little messy) since there was already a property I could check to know if the connection had been disposed of....

Express doesn't do that, node does -- but when I reproduced the error, it was not an unhandled error event -- I didn't bind a handler, but it did not...

The requests themselves will fail anyway; this is not inherently a bug that causes requests to fail -- it's the opposite. A network problem (timeout on reading from socket) causes...

The stack dump after "Sat, 12 Sep 2015 15:36:55 GMT pool2 Successfully allocated new resource (cur=5, ac=0, id=39)" -- did you add that?

Thank you for the stack dump, too. Strangely, it seems to maybe not be the same problem, although sourced through the same files and for the same reason. I see...

You know what, do you have Skype? I have time this weekend and could get on a call so we could cut out all the back and forth... (Add me:...

``` javascript // $ suffix = promisified function function getFoos(args, cb) { var key = 'prepared:1'; return cluster.acquire$(key, false) .tap(function (conn) { if (!cluster.hasCapability(conn, key)) { return prepareStatement$(conn, key) .then(function...

Last thing (I hope!): Currently 'capabilities' is 1:1 with Pool objects; it's used to select specific Pools among many in a Cluster; the usage discussed here is 1:1 with resource...

This was kind of an interest-check at the time, but no, no development is planned. Knex has (unfortunately?) moved away from pool2 to a later version of generic pool due...

Ah, sorry. I wrote this to compensate for some bad edge cases with the normal levenshtein-type algorithm, so the main idea was just to replace that with something with better...