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.14 (2019-01-21, General Availability)

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 using the connection now sets the default schema on the server; that is, subsequent queries executed using session.sql() no longer need to specify the schema.

Bugs Fixed

  • Setting the default schema with a connection URI using a schema name that contained special characters requiring URL encoding resulted in the encoded name being used instead of the original one (for example, %25%26%5E*%5E_ instead of %&^*^_). (Bug #28990682)

  • The client hung when the CA specified by sslOption differed from the certificate authority used to sign the server certificate, or the CA had been revoked. Now in such cases, we once again throw the appropriate error. (Bug #28977649)

  • Attempting to use synonyms for false such as 0, false, null, and undefined raised errors when updating or inserting documents in a collection or rows in a table. In addition, boolean values are now converted to numeric values (true to 1, false to 0) while null and undefined are converted to MySQL NULL. (Bug #28970727, Bug #93315)

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

  • Setting the default schema from the connection string created the schema if it did not exist. Now, an Unknown database error is thrown in such cases instead.

  • It was possible for an empty short-form notice to throw Error: Invalid type for Mysqlx.Notice.Frame on the client. Now these are ignored, as with long-form empty notices.