loopback-connector-mysql

Commit Graph

Author	SHA1	Message	Date
Christiaan Westerbeek	d89ab511c6	Tests for generated columns	2017-01-19 19:00:32 -05:00
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
Ryan Graham	2533fe8404	test: use dump of original test DB as seed	2016-08-09 19:14:51 -07:00

Author

SHA1

Message

Date

Christiaan Westerbeek

d89ab511c6

Tests for generated columns

2017-01-19 19:00:32 -05:00

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

Ryan Graham

2533fe8404

test: use dump of original test DB as seed

2016-08-09 19:14:51 -07:00

3 Commits