MySQL Forums
Forum List  »  Announcements

MySQL Connector/Node.js 8.0.14 has been released
Posted by: Jocelyn Ramilison
Date: January 21, 2019 06:52AM

Dear MySQL users,

MySQL Connector/Node.js is a new Node.js driver for use with the X
DevAPI. This release, v8.0.14, 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.14 (2019-01-21, General Availability)

Functionality Added or Changed

     * Removed deprecation notices from the count() methods.

     * Setting the default schema via the connection now sets
       the default schema on the server; meaning, subsequent
       queries executed using session.sql() do not need to
       specify the schema.

Bugs Fixed

     * Setting the default schema with the connection URI using
       a schema name that contained special characters (that
       would need to be percent-encoded) would result in the
       percent-encoded name being used instead of the original
       one (e.g. "%25%26%5E*%5E_" instead of "%&^*^_"). (Bug

     * An error is once again thrown if sslOption's 'ca' is
       different than the certificate authority used to sign the
       server certificate, or if the server certificate has been
       revoked. (Bug #28977649)

     * Attempting to use false-like values such as 0, false,
       null, and undefined would emit errors when updating or
       inserting documents in a collection or rows in a table.
       Additionally, now boolean values become numeric values
       (true=1, false=0) while null and undefined are converted
       to MySQL's NULL type. (Bug #28970727, Bug #93315)

     * Collection.existsInDatabase() always returned true if any
       other collection existed in the database. (Bug #28745240)

     * Configuring a default schema from the connection string
       would create the schema if it did not exist. Now, an
       "Unknown database" error is thrown instead.

     * An unexpected notice could result in an unexpected halt
       of the client.

On Behalf of Oracle/MySQL Release Engineering Team,
Hery Ramilison

Options: ReplyQuote

Written By
MySQL Connector/Node.js 8.0.14 has been released
January 21, 2019 06:52AM

Sorry, you can't reply to this topic. It has been closed.
This forum is currently read only. You can not log in or make any changes. This is a temporary situation.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.