- no changes. published to update npm docs
- bug fix only
- Pool modifies the Tedious connection object rather than the Connection prototype.
- Added additional log message when acquiring a connection.
- No changes from v0.3.9.
- bug fix only
- bug fix only
- bug fix only
poolConfigoptionminis limited to less thanmax
poolConfigoptionminsupports being set to 0
- Ignore calls to connection.release() on a connection that has been closed or not part of the connection pool.
- Calls connection.reset() when the connection is released to the pool. This is very unlikely to cause anyone trouble.
- Added a callback argument to connectionPool.drain()
- Removed dependency on the
generic-poolnode module. - Added
poolConfigoptionsretryDelay - Added
poolConfigoptionsaquireTimeout(Possibly Breaking) - Added
poolConfigoptionslog idleTimeoutMillisrenamed toidleTimeout(Possibly Breaking)- The
ConnectionPool'error'event added - The behavior of the err parameter of the callback passed to
acquire()has changed. It only returns errors related to acquiring a connection not Tedious Connection errors. Connection errors can happen anytime the pool is being filled and could go unnoticed if only passed the the callback. Subscribe to the'error'event on the pool to be notified of all connection errors. (Possibly Breaking) PooledConnectionobject removed.
- To acquire a connection, call on
acquire()on aConnectionPoolrather thanrequestConnection(). (Breaking) - After acquiring a
PooledConnection, do not wait for the'connected'event. The connection is received connected. (Breaking) - Call
release()on aPooledConnectionto release the it back to the pool.close()permanently closes the connection (asclose()behaves in in tedious). (Breaking)