Showing entries 1 to 3
Displaying posts with tag: connector-nodejs (reset)
Deprecating End-of-life runtime engines on Connector/Node.js

Starting with the 8.0.23 release, Connector/Node.js will be deprecating support for End-of-life Node.js engine versions. Support for these versions will eventually be removed on subsequent releases which will focus on compatibility with the available LTS versions at the date of each release.

Why now?

Up until now, the minimum Node.js engine version compatible with Connector/Node.js was version 4.2.0. This is a fairly old release that has reached End-of-life status in 2018 and, of course, hasn’t been maintained since then. This is also the case for the next two major Node.js versions – v6 and v8 – and will soon (April 30, 2021) be the case for Node.js v10. So, as of today, the oldest LTS version available is effectively Node.js v12, and the …

[Read more]
MySQL Connector/Node.js 8.0.23 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.23, 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

[Read more]
Rethinking Result Sets in Connector/Node.js

It used to be the case where, in order to actually process data retrieved from the database using Connector/Node.js, you would have to resort to an API that required the use of both JavaScript callbacks and Promises. This was meant to provide more flexibility and control to the application developer and at the same time decrease the chance of buffering data unnecessarily. However this wasn’t useful for 99% of the use-cases and made simple tasks a little bit cumbersome. Also, the fact that it required using two different asynchronous constructs made it a little bit harder to grasp.

To make matters worse, in order to consume operational metadata about the columns in the result set, you would have to provide an …

[Read more]
Showing entries 1 to 3