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


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 in this version, Connector/Node.js will ignore compatibility with End-of-life Node.js versions. 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 End-of-life Node.js versions. Today this means only Node.js 12.0.0 or higher are officially supported.

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

  • Improved server disconnection handling of X Protocol connections now creates a log entry and returns an error message, as needed, after Connector/Node.js receives a connection-close notice from the server. Connector/Node.js detects three new types of warning notices.

    • Connection idle notice: 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 the “Connection closed. Reason: connection idle too long” error message.

    • Server shutdown notice: If a connection-close notice is received in a session as a result of a server shutdown, Connector/Node.js terminates the session with the "Connection closed. Reason: server shutdown" error message. All other sessions that are connected to the same endpoint are removed from the pool, if connection pooling is used.

    • Connection killed notice: If the connection being killed 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 the “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)

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