loopback-connector-mysql/test
Carl Fürstenberg 5383c4c0ff Follow mysql recommendations for handling booleans
Per http://dev.mysql.com/doc/refman/5.7/en/numeric-type-overview.html
`BOOL` and `BOOLEAN` is alias for `TINYINT(1)` thus we should make
sure discover can handle as such.

Introducing three flags:

* treatCHAR1AsString
  default false - treats CHAR(1) as a String instead of a Boolean
* treatBIT1AsBit
  default true - treats BIT(1) as a Boolean instead of a Binary
* treatTINYINT1AsTinyInt
  default true - treats TINYINT(1) as a Boolean instead of a Number

The default handling for CHAR(1) is legacy backward compability due to
custom to use a CHAR(1) to store 'Y', 'N', '0', '1', etc...
2017-01-11 19:44:50 -08:00
..
helpers Fix CI Failures 2016-12-07 23:53:46 -05:00
connection.test.js Update eslint infrastructure 2016-08-10 20:04:26 -04:00
datatypes.test.js Fix CI Failures 2016-12-07 23:53:46 -05:00
imported.test.js Update eslint infrastructure 2016-08-10 20:04:26 -04:00
init.js Add connectorCapabilities global object (#201) 2016-10-11 23:13:20 -07:00
migration.test.js Fix CI Failures 2016-12-07 23:53:46 -05:00
mocha.opts Move mocha args to test/mocha.opts 2013-12-13 10:27:33 -08:00
mysql.autoupdate.test.js Fix expected column name when autoupdate 2016-12-12 10:06:18 -05:00
mysql.discover.test.js Follow mysql recommendations for handling booleans 2017-01-11 19:44:50 -08:00
mysql.test.js Add CI fixes (#197) 2016-09-28 13:32:38 -07:00
persistence-hooks.test.js Update eslint infrastructure 2016-08-10 20:04:26 -04:00
schema.sql Follow mysql recommendations for handling booleans 2017-01-11 19:44:50 -08:00
transaction.promise.test.js Update eslint infrastructure 2016-08-10 20:04:26 -04:00
transaction.test.js Update eslint infrastructure 2016-08-10 20:04:26 -04:00