node package manager


fast mysql driver. Implements core protocol, prepared statements, ssl and compression in native JS


Mysql client for node.js. Written in native JavaScript and aims to be mostly api compatible with node-mysql

In addition to client-side query/escape and connection pooling

  • fast
  • MySQL server API for proxies and mocks
  • SSL and compression
  • prepared statements
  • binlog protocol client

See node-mysql documentation. If you see api incompatibilities, please report via github issue.

Below is a list of extensions not supported by node-mysql:

In addition to errback interface there is thin wrapper to expose Promise-based api

   var mysql = require('mysql2/promise'); // or require('mysql2').createConnectionPromise 
   mysql.createConnection({ /* same parameters as for non-promise createConnection */ })
     .then((conn) => conn.query('select foo from bar'))
     .then(([rows, fields]) => console.log(rows[0].foo))
   var pool = require('mysql2/promise').createPool({}); // or mysql.createPoolPromise({}) 
     .then((conn) => {
        var res = conn.query('select foo from bar');
        return res;
     }).then( (result) => {
     }).catch( (err) => {
       console.log(err); // any of connection time or query time errors from above 

es7 async/await:

   let mysql = require('mysql2/promise');
   let conn = await mysql.createConnection({ database: test });
   let [rows, fields] = await conn.execute('select ?+? as sum', [2, 2]);
   let mysql = require('mysql2/promise');
   let pool = mysql.createPool({ database: test });
   // execute in parallel, next console.log in 3 seconds 
   await Promise.all([pool.query('select sleep(2)'), pool.query('select sleep(3)')]);
   console.log('3 seconds after');
   await pool.end();
   await conn.end();

co library:

var mysql = require('mysql2');
var co = require('co')
co(function * () {
  var c = yield mysql.createConnectionPromise({ user: 'root', namedPlaceholders: true });
  var rows = yield c.query('show databases');
  console.log( yield c.execute('select 1+:toAdd as qqq', {toAdd: 10}) );
  yield c.end();

see examples in /examples/promise-co-await

During connection phase the server may ask client to switch to a different auth method. If authSwitchHandler connection config option is set it must be a function that receive switch request data and respond via callback. Note that if mysql_native_password method is requested it will be handled internally according to Authentication::Native41 and authSwitchHandler won't be invoked. authSwitchHandler MAY be called multiple times if plugin algorithm requires multiple roundtrips of data exchange between client and server. First invocation always has ({pluginName, pluginData}) signature, following calls - ({pluginData}). The client respond with opaque blob matching requested plugin via callback(null, data: Buffer).

Example: (imaginary ssh-key-auth plugin) pseudo code

var conn = mysql.createConnection({
  user: 'test_user',
  password: 'test',
  database: 'test_database',
  authSwitchHandler: function(data, cb) {
    if (data.pluginName === 'ssh-key-auth') {
      getPrivateKey((key) => {
        var response = encrypt(key, data.pluginData);
        // continue handshake by sending response data 
        // respond with error to propagate error to connect/changeUser handlers 
        cb(null, response);

Initial handshake always performed using mysql_native_password plugin. This will be possible to override in the future versions.

You can use named placeholders for parameters by setting namedPlaceholders config value or query/execute time option. Named placeholders are converted to unnamed ? on the client (mysql protocol does not support named parameters). If you reference parameter multiple times under the same name it is sent to server multiple times.

   connection.config.namedPlaceholders = true;
   connection.execute('select :x + :y as z', { x: 1, y: 2}, function(err, rows) {
     // statement prepared as "select ? + ? as z" and executed with [1,2] values 
     // rows returned: [ { z: 3 } ] 
   connection.execute('select :x + :x as z', { x: 1 }, function(err, rows) {
     // select ? + ? as z, execute with [1, 1] 
   connection.query('select :x + :x as z', { x: 1 }, function(err, rows) {
     // query select 1 + 1 as z 

Similar to connection.query().

connection.execute('select 1 + ? + ? as result', [5, 6], function(err, rows) {
  // rows: [ { result: 12 } ] 
  // internally 'select 1 + ? + ? as result' is prepared first. On subsequent calls cached statement is re-used 
// close cached statement for 'select 1 + ? + ? as result'. noop if not in cache 
connection.unprepare('select 1 + ? + ? as result');
connection.prepare('select ? + ? as tests', function(err, statement) {
   // statement.parameters - array of column definitions, length === number of params, here 2 
   // statement.columns - array of result column definitions. Can be empty if result schema is dynamic / not known 
   // statement.query 
   statement.execute([1, 2], function(err, rows, columns) {
    // -> [ { tests: 3 } ] 
   // note that there is no callback here. There is no statement close ack at protocol level. 

Note that you should not use statement after connection reset (changeUser() or disconnect). Statement scope is connection, you need to prepare statement for each new connection in order to use it.

var options = {sql: 'select A,B,C,D from foo', rowsAsArray: true};
connection.query(options, function(err, results) {
  /* results will be an array of arrays like this now:
     'field A value',
     'field B value',
     'field C value',
     'field D value',
  ], ...]

In addition to sending local fs files you can send any stream using infileStreamFactory query option. If set, it has to be a function that return a readable stream. It gets file path from query as a parameter.

// local file 
connection.query('LOAD DATA LOCAL INFILE "/tmp/data.csv" INTO TABLE test FIELDS TERMINATED BY ? (id, title)', onInserted1);
// local stream 
var sql = 'LOAD DATA LOCAL INFILE "mystream" INTO TABLE test FIELDS TERMINATED BY ? (id, title)';
  sql: sql,
  infileStreamFactory: function(path) { return getStream(); }
}, onInserted2);
var net        = require('net');
var mysql      = require('mysql2');
var shape      = require('shaper');
var connection = mysql.createConnection({
   user: 'test',
   database: 'test',
   stream: net.connect('/tmp/mysql.sock').pipe(shape(10)) // emulate 10 bytes/sec link 
connection.query('SELECT 1+1 as test1', console.log);

stream also can be a function. In that case function result has to be duplex stream, and it is used for connection transport. This is required if you connect pool using custom transport as new pooled connection needs new stream. Example connecting over socks5 proxy:

var mysql      = require('mysql2');
var SocksConnection = require('socksjs');
var pool = mysql.createPool({
  database: 'test',
  user: 'foo',
  password: 'bar'
  stream: function(cb) {
    cb(null, new SocksConnection({ host: '', port: 3306}, { host: 'localhost', port: 1080 }));

In addition to password createConnection(), createPool() and changeUser() accept passwordSha1 option. This is useful when implementing proxies as plaintext password might be not available.

In contrast to node-mysql, zeroFill flag is ignored in type conversion. You need to check corresponding field zeroFill flag and convert to string manually if this is of importance to you.

DECIMAL and NEWDECIMAL types always returned as string unless you pass this config option:

  decimalNumbers: true

Warning this option could lose precision on the number as Javascript Number is a Float!

Simple select:

var mysql      = require('mysql2');
var connection = mysql.createConnection({ user: 'test', database: 'test'});
connection.query('SELECT 1+1 as test1', function(err, rows) {

Prepared statement and parameters:

var mysql      = require('mysql2');
var connection = mysql.createConnection({ user: 'test', database: 'test'});
connection.execute('SELECT 1+? as test1', [10], function(err, rows) {

Connecting over encrypted connection:

var fs         = require('fs');
var mysql      = require('mysql2');
var connection = mysql.createConnection({
   user: 'test',
   database: 'test',
   ssl: {
     key: fs.readFileSync('./certs/client-key.pem'),
     cert: fs.readFileSync('./certs/client-cert.pem')
connection.query('SELECT 1+1 as test1', console.log);

You can use 'Amazon RDS' string as value to ssl property to connect to Amazon RDS mysql over ssl (in that case CA cert is used)

var mysql      = require('mysql2');
var connection = mysql.createConnection({
   user: 'foo',
   password: 'bar',
   host: '',
   ssl: 'Amazon RDS'
conn.query('show status like \'Ssl_cipher\'', function(err, res) {
  console.log(err, res);

Simple mysql proxy server:

var mysql = require('mysql2');
var server = mysql.createServer();
server.on('connection', function(conn) {
    protocolVersion: 10,
    serverVersion: 'node.js rocks',
    connectionId: 1234,
    statusFlags: 2,
    characterSet: 8,
    capabilityFlags: 0xffffff
  conn.on('field_list', function(table, fields) {
    console.log('field list:', table, fields);
  var remote = mysql.createConnection({user: 'root', database: 'dbname', host:'', password: 'secret'});
  conn.on('query', function(sql) {
    console.log('proxying query:' + sql);
    remote.query(sql, function(err) { // overloaded args, either (err, result :object) 
                                      // or (err, rows :array, columns :array) 
      if (Array.isArray(arguments[1])) {
        // response to a 'select', 'show' or similar 
        var rows = arguments[1], columns = arguments[2];
        console.log('rows', rows);
        console.log('columns', columns);
        conn.writeTextResult(rows, columns);
      } else {
        // response to an 'insert', 'update' or 'delete' 
        var result = arguments[1];
        console.log('result', result);
  conn.on('end', remote.end.bind(remote));
  • createServer() - creates server instance
  • Server.listen - listen port / unix socket (same arguments as net.Server.listen)


  • connect - new incoming connection.
  • serverHandshake({serverVersion, protocolVersion, connectionId, statusFlags, characterSet, capabilityFlags}) - send server handshake initialisation packet, wait handshake response and start listening for commands
  • writeOk({affectedRows: num, insertId: num}) - send OK packet to client
  • writeEof(warnings, statusFlags) - send EOF packet
  • writeTextResult(rows, fields) - write query result to client. Rows and fields are in the same format as in connection.query callback.
  • writeColumns(fields) - write fields + EOF packets.
  • writeTextRow(row) - write array (not hash!) of values as result row
  • TODO: binary protocol


Every command packet received by the server will be emitted as a packet event with the parameters:

  • packet: Packet - The packet itself
  • knownCommand: boolean - is this command known to the server
  • commandCode: number - the parsed command code (first byte)

In addition special events are emitted for commands received from the client. If no listener is present a fallback behavior will be invoked.

  • quit() - Default: close the connection
  • init_db(schemaName: string) - Default: return OK
  • query(sql: string) - Please attach a listener to this. Default: return HA_ERR_INTERNAL_ERROR
  • field_list(table: string, fields: string) - Default: return ER_WARN_DEPRECATED_SYNTAX
  • ping() - Default: return OK

Running the tests requires MySQL server and an empty database.

# Run once to setup the local environment variables. 
export CI=1;
export MYSQL_HOST='';
export MYSQL_USER='root';
export MYSQL_PASSWORD='root';
export MYSQL_DATABASE='test';
# If test user has no password, unset the `CI` variable. 
# Run the test suite 
npm run test

Use FILTER environment variable to run a subset of tests with matching names, e.g.

FILTER='test-timestamp' npm run test


  • Internal protocol is written from scratch using my experience with mysql-native
  • constants, sql parameters interpolation, pool, connection config class taken from node-mysql (I tried to preserve git history)
  • SSL upgrade code based on @TooTallNate code
  • Secure connection / compressed connection api flags compatible to mariasql client.
  • contributors

Feel free to create pull requests. TODO in order of importance:

  • node-mysql api incompatibility fixes
  • documentation
  • tests
  • benchmarks
  • bug fixes
  • TODOs in source code
  • performance improvements
  • features