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
..
discovery.js	Follow mysql recommendations for handling booleans	2017-01-11 19:44:50 -08:00
enumFactory.js	Update eslint infrastructure	2016-08-10 20:04:26 -04:00
migration.js	Fix expected column name when autoupdate	2016-12-12 10:06:18 -05:00
mysql.js	Merge pull request #179 from azatoth/zero_datetime	2016-08-11 09:03:14 -07:00
transaction.js	Update eslint infrastructure	2016-08-10 20:04:26 -04:00