* 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
* make unionAll()'s call signature match union()
consolidates the logic used by union() and unionAll(), allowing the two to be used interchangeably
* use spread args instead of arguments array
* Fix unionAll spread arguments
* [#3033] fix: sqlite3 drop/renameColumn() breaks with postProcessResponse
* When postProcessResponse is configured, and client.processResponse()
returns a Promise (e.g. for custom cases such as sqlite3 dropColumn()),
then that Promise is not awaited, but handed to postProcessResponse,
which might break is (e.g. with Objection's knexSnakeCaseMappers()).
* when reinserting data in the modified table, the rows are now being
handled with the "mapped" identifiers (instead of the unmapped)
* add tests, fix hasColumn
* add hasColumn tests for add mysql + snakeCaseMappers
* Improve tests and fix more cases related to processing
* Fix SQLite-specific tests
* MySQL is not case-sensitive, pg is
* Fix event listener duplication. Start executing more tests in CI; fix broken test.
* Fix listener
* Fix listener
* Fix Node 6 support
* There doesn't seem to be a clear way to fix listener behaviour in Node 6, so let's just ignore it for the time being, especially considering that we are dropping support for Node 6 in April anyway.
* Update migration guide
* Align signature for PG datetime and timestamp methods with documentation. Add precision support
* Remove redundant method
* Add upgrade note for the change
* Changes after code review
* Improve API
* Update table column .enu to take an option that does not manually create the type
* Add tests for psql enum existingType
* Avoid utilizing enum values when using an existing type
* Add support for named unique, primary and foreign keys to SQLite3
* Add integration testing for named keys
* Improve tests for primary and unique keys
* Improve tests for foreign keys
* Run prettier
* Fix tests
* Fix additional test
* Pass migration config object as an argument to the migrations themselves, to allow custom parameters to be set for migrations. (#2014)
* Run prettier
* Remove unneeded change
* Remove more unneeded changes
* Fix Node 10 support
* Update documentation based on a new design
* Restore test execution (oops)
* Fix withUserParams method
* Fix knex instance cloning
* Remove unused import
* Fix reference to knex from migrator
* Do not lose user params on transactions
* Remove unneeded require
* Address review comments
* Fix setting event emitter and listeners on Knex copies. Use knex copies to run tests in CI
* Remove knex cloning
* Fix event listener leak
* Introduced abstraction for getting migrations
This would allow a webpack migration source which is compatible with bundling.
* Fixed migration validation with custom migration source
* Fixed issues after rebasing on muti directory PR
* Renamed parameter and fixed error message
* Addressed some PR comments
* Finished comment
* Moved filename extension filtering into fs-migrator
* Added test showing in memory custom migration source
* Cleaned up how to get config
* Fixed failing test
* Hopefully fix tests
* Fix Node.js 10 support in tests
* Use columnize instead of wrap in using().
This is an attempt to fix#2136. Also added an integration test, couldn't find any existing.
* Exclude MSSQL from test as it does not support .using
* Change test to not use subquery
* Change test
* Implement fail-fast logic for dialect resolution, clean-up code around.
* Remove method that was deprecated long time ago
* Address additional comments
* Try addressing comments
* Set client explicitly
* Fix compatibility with older Node versions
