Important Change:Starting with this release, Connector/Node.js ignores compatibility with Node.js versions that have reached their end of life. If you are planning to upgrade, make sure you are using Node.js 12.0.0 or higher.
Connector/Node.js no longer guarantees compatibility with Node.js versions that have reached their end of life. This means that, as of this release, Connector/Node.js officially supports Node.js versions 12.0.0 and later only.
Improved the inline documentation and added functionality for users to generate it locally using JSDoc. See
CONTRIBUTING.md
for instructions on how to generate the HTML documentation.服务器断开处理connec X协议tions has been improved such that it now creates a log entry and returns an error message, as needed after Connector/Node.js receives notice of a closing connection from the server. Connector/Node.js detects three new types of warning notices.
连接空闲: This notice applies to a server connection that remains idle for longer than the relevant timeout setting. Connector/Node.js closes the connection when it receives the notice in an active session or while a new session is being created. An attempt to use the invalid session returnsConnection closed. Reason: connection idle too long.
Server shutdown: If notice of a closing connection is received in a session as a result of a server shutdown, Connector/Node.js terminates the session withConnection closed. Reason: server shutdown. If connection pooling is in use, all other sessions that are connected to the same endpoint are removed from the pool.
Connection killed: If the connection being killed was made from another client session, Connector/Node.js closes the connection when it receives the notice in an active session or while a new session is being created. An attempt to use the invalid session returnsConnection closed. Reason: connection killed by a different sessionerror message.