When converting null values
to database column values,
return null if column is
nullable, otherwise try
to cast it to the property
type, and if not, return
'null'.
MySQL expects reverse order of latitude and longitude
from the way we use it in LoopBack, so switch the order
when saving and loading Point spatial type we use for
Point/GeoPoint.
* Add http status code translations for errors (Kevin Delisle)
* Allow explicit data types (ssh24)
* Revert "switch long and lat for geopoint type" (biniam)
* switch long and lat for geopoint type (biniam)
* Escape index names (#280) (Sakib Hasan)
* Fix docker setup (#279) (Sakib Hasan)
* Add docker setup (#278) (Sakib Hasan)
* Adding support for fractional seconds. (Joost de Bruijn)
* fix compare of foreign keys for autoupdate (#272) (Sergey Nosenko)
* Update README.md (Antoine LA)
* Add docker setup
Add a setup script that spawns a docker container before running test
Easy for contributors now to test, no need for a local instance
* Update readme with docs on running test
* Allow check for container status
Check for if the container is up before proceeding
* Add options for customized user,pass,port
* Fix seeding on database
Only seed the database if user specifies CI=true
OR when the tests actually run on the CI
* Update readme with windows env var
* fix compare of foreign keys for autoupdate
use mysql table name in case it is not equal model name
* fix column name lookup for fk definition
* fix ADD CONSTRAINT for multiple fk
if more the one foreign key added ADD CONSTRAINT
must be separated with comma but not with space as applySqlChanges do.
* fix duplicate foreign key creation on autoupdate
* fix entity name selection
* change join to toString as requested
* fix removing dropped keys
* fix linter issues
* add test case with columnName in foreign key
and isActual check after autoupdate
* uncommit accitenally commited test case
This commit contains all previous work after rebase went badly
RE: Pull Request requested by @kjdelisle regarding #149 following my
proposed solution "A" at #149 (comment).
As mentioned in the post linked above, this change allows the
underlying mysqljs/mysql module to handle Date object serialization
and removes the forced conversion of Dates to UTC Strings.
An opt-out fallback to forced coercion to UTC is included,
which was modeled after #265 from @darknos .
Old, squashed commits:
d0ea1d926eae04d0355109c87eef4eeec173f887
Legacy UTC date processing fallback credit: @darknos
a59dad7d7bd945895fb410a963cf5932b6a20f9e
Remove orphaned string functions
e8fdbdcfd4092f3d9e018f688d14def3e3ca9856
Incorporate @darknos expanded check for zero dates
abd4e0a7e9122f857974678a6b6ad87a19988f6f
Remove DATE manipulations in from/toColumnValue
* refactor date, timestamp, datetime data-type
* reverse datatypes.test.js changes
* checking property.mysql.dataType
along with property.dataType for timestamp fields
* Fix PR linter
* moved test cases all under one test file
remove unnecessary test cases, unify setup procedures
* Fix sql mode before migration
Set sql mode to allow zero's on timestamp
Clean up code
* remove test cases with strings and DATE field type
* code cleanup as requested
* add accidentally deleted assert.ok(found)
* fix timeZone to timezone case in README.md
* Update readme with date type info
Tetsuo Seto
Tetsuo Seto
Sakib Hasan
ssh24
Biniam Admikew
biniam
Kevin Delisle
Kevin Delisle
Janny
Joost de Bruijn
Sergey Nosenko
Diana Lau
Antoine LA
Buck Bito
Benjamin Schuster-Boeckler