* Fixed some of the tests failing with various dialect combinations
* Setup all test databases to run in docker
* Fixed test suite and updated travis to use docker
* Fixed some tests in master and disabled oracle tests while setting everything else to work again
* Changed docker to use latest postgresql alpine image
* Re-enabled all oracledb tests
* Install oracle client libs to oracle server and copy them to travis to make node oracledb package to work
* Disabled random failing oracle tests and added test to show that oracle update in transaction does not seem to work ACID
* Update package.json
* Update package.json
* Fixed linting issues
* Fixed waiting for postgres to use the same DB image that database is using.
* Removed installing oracledb driver in travis if not needed .travis.yml
* Cleaned up package.json more
* Created static name for oracledb container to allow copying files out of it on different docker versions
* Removed webpack from deps
* Normalized and validated driverNames of test db clients and fixed oracle test setup
* Fixed failed queries from old query building tests which hadn't been ran in ages
* Allow selecting node version which is used to run oracledb docker tests
* Improved sql tester error messages
* Fixed rest of the oracledb tests
* Removed invalid flag from docker-compose
* Print mssql logs if initialization fails
* Fixed syntax error + final tests
* Added restart of failure for mssql DB initialization to try again if server was not ready
* Printout always mssql logs after container is started
* Fixed wait time printing after trying to connect
* Use npm run oracledb:test for testing oracle in travis
* Run SQL Server tests locally running SQL server in docker
* Made oracledb test script naming consistent with mssql
* Updated documentation with more info about oracledb and mssql testing
There has been many PRs which are changing what kind of queries are sent to DB without any real tests that also checks that sent queries are doing the things that they are supposed to do. To be able to make sure that those new queries actually work, in addition to unit tests it is crucial to have some integration tests as well to be able to guarantee that everything won't be broken after the changes.
- Add 'npm run babel' command and run it on 'npm test' (supersedes PR #1011 - Ensure /lib is up to date during CI tests)
- Fix 'npm test' command not working on Windows due to Istanbul config issue (see https://github.com/gotwarlost/istanbul/issues/90)
- Update CONTRIBUTING.md
In MySQL if a savepoint is missing, it means something
else (most likely DDL) triggered an implicit commit. In this
case rather than erroring, let's give a warning message
so it's possible to use the same codepath as a DB where
this actually works.
