mssqldependency has been upgraded from 6.x to 9.x. See the changelog for that package for a list of changes that may be required to your configuration options.- Node >=14 is now required
- defaultConnectionPoolFactory is now exported at the root of the module, making it easier to create a custom connection pool factory that extends the default behavior.
- Cleaned up some npm audit errors (all on devDependencies).
- Added missing
@babel/runtimedependency.@babel/plugin-transform-runtimewas added in0.5.0, which expects@babel/runtimeas a runtime dependency.
No known breaking changes, but we're being cautious with a major version bump since so many packages were updated.
- Updated all packages to latest
- Linting fixes
- Fixed error reporting on streams (not all errors were being emitted)
- New
healthyproperty in pool stats which indicates whether or not a pool was capable of serving requests since the last request was served. This means that the secondary pool could show as healthy but actually be unhealthy because it hasn't served any requests recently. If the primary pool shows as healthy, it's likely in a healthy state if it's receiving any semblance of traffic. - New
acquireTimeoutMillisandcreateTimeoutMillisproperties added to pool stats. These are the timeouts used by thetarnpool inside themssqlpackage.
- No more stuck requests, resource churn, and broken failover when a database goes down.
0.3.*suffered from a bug in themssqlpackage due to some unexpected/broken behavior ingeneric-pool.mssqlwas bumped to6.0.0-alpha.2, which replacedgeneric-poolwithtarn. - The
lastPromotionAtandlastHealAtstats should propagate to new pools after a heal.
- Bumped
mssqlfrom^4.3.0to6.0.0-alpha.2. We do not believe there are any breaking changes inmssql-pool-partyfor this upgrade, but themssqlbump brings with it bumps in thetediousdriver and other internal changes which could be impacting. That, coupled with the alpha state ofmssqlmeans we're doing a major bump to be safe.
- Improved integration tests to handle failover, healing, and promotion scenarios by introducing a second mssql container.
- Properly close unhealthy connections (PR #7, thanks @DullReferenceException!)
- Upgrade node-mssql to
^4.3.0.
- Upgrade node-mssql to
^4.2.1. This paves the way for supporting Availability Groups (more testing needed on this front). - Better DEBUG logging
- Added the following properties to the stats output:
config.appName,config.encrypt.
- Added workaround for tediousjs/node-mssql#705 until it's fixed upstream. This isn't a bug in a previous version, but in node-mssql v4.
- Since mssql-pool-party is a wrapper around node-mssql that aims to minimize interface changes, all breaking changes in node-mssql v4 are relevant to this new version, see here for those changes.
- All responses from Request methods (query, execute, etc), for each style (promise, cb, stream), have been unified to match the changes made in v4. They all return a single object (and an error, if applicable). The result object will look something like the following (first example applies to callback/promise/async-await, second example applies to stream). See README.md for richer documentation.
{
output: {},
recordset: [{}],
recordsets: [
[{}],
],
returnValue: 0,
rowsAffected: [],
}
{
columns: {
ColumnName: {},
},
output: {},
returnValue: 0,
rows: [{}],
rowsAffected: [],
}
- Removed the following properties from the stats output:
config.driver,config.tdsVersion,timeouts.cancel, - Enable the
encryptdriver options by default. Disabled by default has already been deprecated intediousand will be removed in a newer version, we're just jumping ahead a little to get rid of an annoying console message. If you don't want encryption, use this config:
connectionPoolConfig: {
options: {
encrypt: false
}
}
- Upgrade jest and babel-jest from
^19.02to^23.6.0 - Removed jest-environment-node-debug and jest-unit from devDependencies
- Enabled test coverage, dropped requirement to 75% (goal of 100% in future)
sqlcmdis now on the PATH inside the integration test Docker container- Fixed some bugs involved with running tests in parallel
- Added missing stream tests
- Added package-lock.json
- Fixed a bug in the default raceWarmup strategy that was incorrectly resolving the warmup if a pool failed to connect properly. This should make initial connections a little more reliable.
- Added priority to stats output.
- Fixed a bug in the reconnect process that was uncovered by the bug fix in 0.2.1. In 0.2.1, we started detecting pool healing failures correctly, which started triggering a condition in the reconnect process that prevented a reconnect if no pools were healed, which turned out not to be desirable. Now, if no pools were healed during a reconnect, it jumps right to another heal attempt.
- Added optional pool prioritization. This feature is intended to provide a means to failback to a preferred DSN after previously promoting a lower priority DSN. See here for configuration options.
- Fixed a bug in the heal process that was preventing heal failures from being detected properly in most cases. This will prevent unnecessary retries against unhealthy pools.
- The
poolproperty has been removed from thePoolErrorclass due to concerns about exposing references to internal connections and DSNs. There is now adsnproperty which contains information about the DSN owned by the pool involved in the error.
- Version bump with no change in functionality. This was done to avoid conflits with a previous version hosted on our internal registry.
- Improved debug logs
- All debug logs go to stdout
- No changes in production functionality
- Fixed error when running
connection.request().query('...')commands that did not return a recordset (e.g.TRUNCATE TABLE ...)
- Added a high-write integration test
- Added unit test
- Added a bit more debug logging
- Removed pool.dsn.password from PoolError to avoid passwords showing up in error logging
- Fixed returnValue not being return when calling execute
- Fixed broken execute callback tests
- Added
connectionPoolConfigoption to the ConnectionPoolParty constructor. This new option lets you set configuration options that will be passed to the mssql ConnectionPool constructor. This provides a way to set things like timeouts without having to create a custom connectionPoolFactory or dsnProvider. Note: any options set here will override options created by the dsnProvider
First Release!