public / sequelize

- adds hasTrigger option in model.js that is then passed to
querygenerator.update
- adds integration test for Model.update

Include the error message in the exception to ease debug

fix(belongs-to-many): properly pair association based on the through …

update should pass options to set

…ons.through, not a reference

Currently the options are not passed along, which breaks ssaclAttributeRoles and might break other plugins.
Generally all options should just be propagated (unless they need to removed cause they will break the method).

The code would previously pair association based on the through.model argument of the original options.
However options.through.model would generally be undefined since users usually just pass through: Model and the normalization to through.model
actually happened on association.through rather than options.through.
Normalization now happens on the options set before being assigned to association.through

[ci skip] docs(transaction) Fix the bug in transactiona document.

The previous example code is buggy because you need get specified isolation level from Sequelize.Transaction.ISOLATION_LEVELS instead of Sequelize.Transaction.

[ci skip] doc(querying) Add documentation for the $notIn query operator.

…porarily move mssql to allowed failures

Add default validation based on attribute type

Do not add a transaction in findOrCreate if there is none. Fixes #4133

Add testcase and fix the unit test

Sequelize doesn't compare dates correctly

… it before commit / rollback

…re prepended to attribute names to prevent ambiguity errors

feat(has-many): countAssociations

feat(belongs-to-many): countAssociations