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


MySQL Connector/Node.js Release Notes  /  Changes in MySQL Connector/Node.js 8.0  /  Changes in MySQL Connector/Node.js 8.0.18 (2019-10-14, General Availability)

Changes in MySQL Connector/Node.js 8.0.18 (2019-10-14, General Availability)

Functionality Added or Changed

  • Implemented the X DevAPI cursor model, including methods such as fetchOne(), fetchAll(), getColumns(), hasData(), and nextResult(). For more information, see Working with Result Sets, in the X DevAPI documentation.

    Previously, handling result set data or metadata required specific callback functions when calling execute(). With the addition of this interface, the Connector automatically switches to the pull-based cursor model if these callback functions are not provided.

  • Improved the performance of Collection.getOne() by parsing the underlying lookup expression only once, and using serverside prepared statements for subsequent calls to this method.

  • Added support for generating test coverage reports by running the npm run coverage or similar commands; see the bundled CONTRIBUTING.md file for requirements and other information. This was added to help users make contributions.

  • Added linter check support to help enforce coding style and convention rules for new contributions by running npm run linter; see the bundled CONTRIBUTING.md file for more information.

Bugs Fixed

  • Added support for assigning Node.js Buffer values to expressions and query placeholders. (Bug #30163003, Bug #96480)

  • MySQL column values of binary types such as BLOB, BINARY, and VARBINARY can now be converted to instances of Node.js Buffer. (Bug #30162858, Bug #96478)

  • Inserting a raw Node.js Buffer value into a MySQL BLOB column resulted in an error due to improper setting of the content_type; now the X Plugin handles this as a raw byte string. (Bug #30158425)

  • The padding characters used for fixed-length columns now map to the collation code provided by the column metadata; previously it was based on the JavaScript native type of the values. (Bug #30030159)