MySQL Blog Archive
For the latest blogs go to
MySQL Connector/Node.js 8.0.17 has been released

Dear MySQL users,

MySQL Connector/Node.js is a new Node.js driver for use with the X
DevAPI. This release, v8.0.17, is a maintenance release of the
MySQL Connector/Node.js 8.0 series.

The X DevAPI enables application developers to write code that combines
the strengths of the relational and document models using a modern,
NoSQL-like syntax that does not assume previous experience writing
traditional SQL.

MySQL Connector/Node.js can be downloaded through npm (see for details) or from

To learn more about how to write applications using the X DevAPI, see
For more information about how the X DevAPI is implemented in MySQL
Connector/Node.js, and its usage, see

Please note that the X DevAPI requires at least MySQL Server version
8.0 or higher with the X Plugin enabled. For general documentation
about how to get started using MySQL as a document store, see

Changes in MySQL Connector/Node.js 8.0.17 (2019-07-22,
General Availability)

Functionality Added or Changed

*Document fields containing arrays can now be indexed by setting array to true in an index fields definition.

*Added support for the OVERLAPS and NOT OVERLAPS operators; which is equivalent to the SQL JSON_OVERLAPS() function. These binary operators are used with a general “expression operator expression” syntax; and the expressions return a JSON array or object. Example usage: [1, 2, 3] overlaps $.list

*Added support for the utf8mb4_0900_bin collation added in MySQL Server 8.0.17.

*The bundled file was split and reformatted with some content moved into the new README.txt and files.

Bugs Fixed

*The SQL CAST function did not work as a valid lookup expression. (Bug #29807792)

*Added backtick support for table column identifiers in valid expressions. (Bug #29789818)

*The DIV binary and NOT unary operators are now allowed; and are case-insensitive. (Bug #29771833, Bug #29771027) * Collection.find() now supports the JavaScript Date type. (Bug #29766014)

*The collection.dropIndex method now silently fails if the index does not exist, as expected, when before it generated a “Can’t DROP” error. (Bug #29765589)

*Column.getCollationName() would potentially return the incorrect name. (Bug #29704185

On Behalf of MySQL/ORACLE RE Team
Gipson Pulla