Documentation Home
MySQL Connector/Node.js Release Notes
Download these Release Notes
PDF (US Ltr) - 126.0Kb
PDF (A4) - 125.1Kb


MySQL Connector/Node.js Release Notes  /  Changes in MySQL Connector/Node.js 8.0  /  Changes in MySQL Connector/Node.js 8.0.24 (2021-04-20, General Availability)

Changes in MySQL Connector/Node.js 8.0.24 (2021-04-20, General Availability)

Functionality Added or Changed

  • 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.

  • Server disconnection handling of X Protocol connections 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.

    • Connection idle: 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 returns Connection 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 with Connection 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 returns Connection closed. Reason: connection killed by a different session error message.

Bugs Fixed

  • The getSession() method now releases connections from a pool when an exception is raised while connecting to the server. (Bug #32366743, Bug #101928)

  • Session.getDefaultSchema() returned 'undefined' instead of a valid Schema instance if a default schema was not set. (Bug #32136490)