2.4.0

This version is a Stable (GA) release.

Full Changelog

This version removes compatibility with Node.js 6, needing 10+ version!

• CONJS-86 - Support extension type format
• CONJS-128 - Error when using multipleStatements with metaAsArray
• CONJS-129 - Support 10.5 pluggable type
• CONJS-131 - checkDuplicate option is indicated in error when having dupplicate
• CONJS-132 - performance improvement
• CONJS-136 - typescript SqlError interface

MariaDB connector/node.js 2.3.1

This version is a Stable (GA) release.

Full Changelog

Corrective release of 2.3.0, changing new connection option timeout to queryTimeout to avoid any confusion.

MariaDB connector/node.js 2.3.0

This version is a Stable (GA) release.

Full Changelog

• CONJS-127 - Resultset with same identifier skip data. Now an error will be thrown.
• CONJS-126 - permit setting session query timeout per option
• CONJS-124 - Force connection.escapeId to emit backtick #101
• CONJS-123 - exporting SqlError class to permit instanceOf checks #100
• CONJS-122 - fix undefined localTz with timezone: 'Z' issue #92
• CONJS-121 - Connection.escapeId must always quote value to permit reserved words

misc:

• appveyor testing server version upgrade
• better debug logging trace format
• correct ssl test

MariaDB connector/node.js 2.2.0

This version is a Stable (GA) release.

Full Changelog

CONJS-119 Add an option to detect Server version using a dedicated SELECT @@Version

Azure is using a proxy that will return a MySQL handshake not reflecting real server.
A new option `forceVersionCheck` is added to permit issuing a new `SELECT @@Version` command on connection creation, 
to retrieve the correct server version. Connector will then act according to that server version.

CONJS-20 add query timeout implementation

This option is only permitted for MariaDB server >= 10.1.2, and permits to set a timeout to query operation. 
Driver internally use `SET STATEMENT max_statement_time=<timeout> FOR <command>` permitting to cancel operation when timeout is reached, 

Implementation of max_statement_time is engine dependent, so there might be some differences: For example, with Galera engine, a commits will ensure replication to other nodes to be done, possibly then exceeded timeout, to ensure proper server state.

example:

//query that takes more than 20s
connection
  .query({sql: 'information_schema.tables, information_schema.tables as t2', timeout: 100 })
  .then(...)
  .catch(err => {
          // SQLError: (conn=2987, no: 1969, SQLState: 70100) Query execution was interrupted (max_statement_time exceeded)
          // sql: select * from information_schema.columns as c1, information_schema.tables, information_schema.tables as t2 - parameters:[]
          // at Object.module.exports.createError (C:\projets\mariadb-connector-nodejs.git\lib\misc\errors.js:55:10)
          // at PacketNodeEncoded.readError (C:\projets\mariadb-connector-nodejs.git\lib\io\packet.js:510:19)
          // at Query.readResponsePacket (C:\projets\mariadb-connector-nodejs.git\lib\cmd\resultset.js:46:28)
          // at PacketInputStream.receivePacketBasic (C:\projets\mariadb-connector-nodejs.git\lib\io\packet-input-stream.js:104:9)
          // at PacketInputStream.onData (C:\projets\mariadb-connector-nodejs.git\lib\io\packet-input-stream.js:160:20)
          // at Socket.emit (events.js:210:5)
          // at addChunk (_stream_readable.js:309:12)
          // at readableAddChunk (_stream_readable.js:290:11)
          // at Socket.Readable.push (_stream_readable.js:224:10)
          // at TCP.onStreamRead (internal/stream_base_commons.js:182:23) {
          //     fatal: true,
          //         errno: 1969,
          //         sqlState: '70100',
          //         code: 'ER_STATEMENT_TIMEOUT'
          // }
  });

CONJS-110 fast-authentication improvement:

  * add mysql_native_password to fast-authentication path
  * plugin 'mysql_native_password' is used by default if default server plugin is unknown
  * unexpected packet type during handshake result will throw a good error.

CONJS-117 Implement a pool leak detection

A new option `leakDetection` permits to indicate a timeout to log connection borrowed from pool.
When a connection is borrowed from pool and this timeout is reached, a message will be logged to console indicating a possible connection leak.
Another message will tell if the possible logged leak has been released.
A value of 0 (default) meaning Leak detection is disable   
Additionally, some error messages have improved:
- Connection timeout now indicate that this correspond to socket failing to establish
- differentiate timeout error when closing pool to standard connection retrieving timeout

misc:

• CONJS-120 Permit values in SQL object to permits compatibility with mysql/mysql2
• CONJS-118 missing import for Error when asking for connection when pool is closed. Thanks to @WayneMDB
• correcting typescript import of @types/node to version >8 thanks to @SimonSchick
• dependencies update

MariaDB connector/node.js 2.1.5

minor evolutions:

Full Changelog

• CONJS-115 Batch improvement
  • supporting array of parameters if only one parameter per query, not only array of array
  • supporting empty array for query without parameters
• correction on licence tag: LGPL-2.1-or-later (was tag LGPL-2.1+ that is deprecated)
• dependencies update

MariaDB connector/node.js 2.1.4

This version is a Stable (GA) release.

Changelog

Full Changelog

• CONJS-112 use pool reset only for corrected COM_RESET_CONNECTION
• CONJS-111 missing pool event definition
• dependencies update

MariaDB connector/node.js 2.1.3

This version is a Stable (GA) release.

Changelog

Full Changelog

• CONJS-109 Missing mysql only collation definition
• CONJS-108 typescript escape/escapeId definition
• CONJS-107 Change user callback function not called when no option is set and changing collation only if collation option is correct
• CONJS-106 properly escape boolean parameter false
• CONJS-105 Typecast provided date function erroneous parsing
• CONJS-104 Pam authentication must permit to provide multiple passwords

misc:

• better cluster error when pool is full
• adding test coverage

MariaDB connector/node.js 2.1.2

This version is a Stable (GA) release.

Changelog

Implemented enhancements:

• CONJS-101 Escape functions API
• CONJS-100 Improve performance using reusable Object type for column definition result
• CONJS-102 Expose library version to API

Fixed bugs:

• CONJS-96 TypeScript definition typecast correction
• CONJS-95 Pool idle maintainer error
• CONJS-98 Missing collation option in typescript definition
• CONJS-99 Improve documentation for best practice concerning credential
• CONJS-97 Remove coverage comment on GitHub pull request

MariaDB connector/node.js 2.1.1

This version is a Stable (GA) release.

Changelog

• node.js v12 CI testing
• cluster ordered selector bug fix on failover (thanks to @kkx)
• bump dependencies
• documentation update with node.js v12 minimum TLSv1.2 default support
• connection.reset() error message improvement (and documentation)
• small performance improvement when debug not enable

MariaDB connector/node.js 2.1.0

This version is a Stable (GA) release.

Changelog

• [CONJS-19] implement Ed25519 plugin
• [CONJS-57] Multiple alternative authentication methods for the same user (MariaDB 10.4)
• [CONJS-61] Permit handling expired password
• [CONJS-85] Implement pool events according to mysql/mysql2 API
• [CONJS-87] Array parameter automatic conversion
• [CONJS-89] Performance improvement on decoding string
• [CONJS-88] Charset collation option separation
• [CONJS-74] Types definition must be string, not byte when using option typeCast
• [CONJS-75] Missing import dependencies for typeScript
• [CONJS-79] Read errors while processing LOCAL INFILE can causes process crash
• [CONJS-83] Add poolCluster 'remove' event
• [CONJS-84] option restoreNodeTimeout is not respected when removeNodeErrorCount is set
• [CONJS-73] Setting timezone to current IANA might provoque server automatic retrieval

New Options

option	description	type	default
collation	(used in replacement of charset) Permit to defined collation used for connection. This will defined the charset encoding used for exchanges with database and defines the order used when comparing strings. It's mainly used for micro-optimizations	string	UTF8MB4_UNICODE_CI
permitConnectionWhenExpired	Permit a user with expired password to connect. Only possible operation in this case will be to change password ('SET PASSWORD=PASSWORD('XXX')')	boolean	false

The option charset now corresponds to charset, still permitting collation for compatibility, but then a warning is thrown to console.