mysql2 reports EPIPE error instead of ER_BAD_FIELD_ERROR

I’m using mysql2 in knex, which in turn is used in a bookshelf model.

When I attempt to insert a model that has a field that doesn’t exist in the table mysql2 returns this error:

{ [Error: insert into `test_table` (`create_time`, `text1`, `text2`, `text3`, `text4`, `nonexistent_column`, `text5`) values ('2016-05-04 15:52:17.174', 'http://google.com', '2016-05-04 15:52:11.512', 'http://yahoo.com', 2, 3, 1
) - This socket has been ended by the other party] code: 'EPIPE', fatal: true }

However, given the exact same scenario but using mysql instead the error is:

[Error: insert into `test_table` (`create_time`, `text1`, `text2`, `text3`, `text4`, `nonexistent_column`, `text5`) values ('2016-05-04 16:05:54.726', 'http://google.com', '2016-05-04 16:05:46.093', 'http://yahoo.com', 2, 3, 1
) - ER_BAD_FIELD_ERROR: Unknown column 'nonexistent_column' in 'field list']

This is incredibly misleading and I’m not sure why EPIPE is returned by mysql2 (or maybe it’s knex?).

mysql2 version is 1.0.0-rc.1. mysql version is 2.10.2

[diversario]

FYI, this what it turned out to be https://github.com/felixge/node-mysql/issues/1411

Connection was lost due to db failover and the pool library that knex uses didn’t reacquire one automatically.

[diversario]

Sure!

The table is as follows:

CREATE TABLE `test_table` (
  `id` int(10) unsigned NOT NULL AUTO_INCREMENT,
  `text5` int(10) unsigned NOT NULL,
  `text4` int(10) unsigned NOT NULL,
  `text1` text,
  `text3` text,
  `text2` datetime NOT NULL,
  `create_time` datetime NOT NULL,
  PRIMARY KEY (`id`),
  UNIQUE KEY `ux_text5` (`text5`),
  KEY `ix_text4` (`text4`),
  KEY `ix_create_time` (`create_time`)
) ENGINE=InnoDB AUTO_INCREMENT=1 DEFAULT CHARSET=utf8mb4

and data being inserted is

{
  text5: 1,
  text4: 2,
  text1: 'http://google.com',
  text3: 'http://yahoo.com',
  nonexistent_column: 3,
  text4: new Date()
}