public / sequelize

* slice the options argument if the logging is set to console.log

* added test case to check if the options object is available for custom logging function, this test case has been added for the pull request 'slice the options argument if the logging is set to console.log (#7555)'

Previous one was giving 404.

* docs: first esdoc steps

* remove: deprecated articles

* fix: a bit of indentation

* add: router with redirects for surge

* fix: small css fixes (hide docs links). fix docs command

* add domain to travis.yml

* chore(package): remove unused packages, add esdoc

* fix: lint

* fix: links in /docs + other small changes

* shields

* remove eslint comments. Add back UnknownConstraintError

* Manual eslint fixes in test

* Manual eslint fixes in lib

* 🔥 remove jshint

* eslint --fix

* 'clarifying the return value of findOrCreate'

The documentation of findOrCreate previously had no precise indication of what to expect findOrCreate to return. I added that it returns an array with two parts in the comments that had already existed in the examples.

* minor typo fixes

* Made some wording changes for tense

* Fix `showIndex()` query regexp

* [ci skip] changelog for #7492

* Added add, remove & show constraints feat

* Added showConstraintsQuery for postgres & mysql

* [ci skip] Added docs for constraints usage

* Added removeIndex support for mysql

* Added altering constraints to sqlite dialect

* Refactor onDelete, onUpdate to work in sqlite dialect

* Throw non existent constraints in removeConstraint query as UnknownConstraintError, improve test coverage

* Fix failing tests

* Removed dialect naming check in favor of dialect.supports feature check

* Improve code coverage, eslint fixes

* Review fixes

* Review fixes

* Renamed model, key to table, field for foreign key contraint definition

* run hooks during validation by default

* Revert "run hooks during validation by default"

This reverts commit da66b72bce4bc274f10745ec98cad86ccb1def20.

* hooks by default

* write validation sequence more cleanly and migrate instance validator integration tests to unit tests

* remove only

* ignore w30

* change log

* fix jshint error and use const

* jshint fix

* only validationFailed  hook when validation fails

* fix changelog

* fix changelog

* add integration tests back

* fix indentation

* and fix spacing

* final code review changes

https://github.com/sequelize/sequelize/issues/7404

* Added feature to alter tables on sync. Fixes #537

* Added an entry to future in changelog

* Added integration test for syncing with alter

* Fixed tests and model with sqlite and psql

* Updated docs and updated some code style

* Updated test.sync.js to use let instead of var

* Changed all vars to lets and replaced anonymous functions with arrow functions

* Added back some anonymous functions to use scope and fixed more coding style

* Updated code style again - removed binds and nested then's

* Updated changelog; renamed and improved tests; Added option to comment

* Changed debug vars to consts

* Switched changes to const

* Added some missing semi-colons

* issue # 7318

fixes issue # 7318 - https://github.com/sequelize/sequelize/issues/7318

* test and change log

* formatting

* changed message

* Update changelog.md

* Update removeAttribute.test.js

In generating the bulk insert query, the serials are stored in an
array. This array can potentially be up to size N, which is the number
of rows to be created.

When generating the tuples at a later stage, we walk through the
records one-by-one - O(N) iterations. However, in a single iteration,
we were performing a lookup in the serials array (indexOf costs O(N)),
leading to a O(N^2) runtime and poor performance for large number of
records inserted.

This patch converts the serials array into an object map instead, so
lookups cost O(1) time.

This fixes #6606

https://greenkeeper.io/

* Expose OptimisticLockError on Sequelize object (#6637)

* Future changelog entry

…chriso/validator.js/issues/618)

Small typo

* performance this Array.concat with for loop/push

for loop/push is much faster than Array.concat.
For the largest/ugliest queries, this can get
called hundreds of thousands of times, so the
performance difference does matter.

* add message to changelog.md

https://greenkeeper.io/

* Added unique indexes to rawAttributes

* Add changelog entry

* Added integration test to cover composite unique keys, review fixes

* Fixes failing tests

* Add quotes around column names for unique constraints in sqlite (fixes #4407)

* Changelog linked to issue