public / sequelize

Closes #5387

…e mssql dialect's describeTableQuery (#5852)

* added failing test case for LIKE ANY parentheses issue

* wrap ANY arguments with parentheses when using LIKE + ANY

* changelog entry for #5736

No instances in params for bulk commands; see https://github.com/sequelize/sequelize/blob/master/lib/hooks.js#L58

https://greenkeeper.io/

https://greenkeeper.io/

https://greenkeeper.io/

* Fixing associations doc

* Updating to nest where and attributes back under include

plus minor edit

https://greenkeeper.io/

* docs(datatype): add a note about BIGINT datatype conversion to string

This helps users to understand the reason to this conversion and avoid more open issues to Sequelize like these:
- https://github.com/sequelize/sequelize/issues/1774
- https://github.com/sequelize/sequelize/issues/4550

* docs(datatype): add documentation to source code

As described in https://github.com/sequelize/sequelize/issues/3302#issuecomment-199238449

* Refactor type validation on value escape

* Fix type validation for a list of values

* Fix type validation for incomplete UUIDs

Useful for instance for fuzzy searching (e.g. the LIKE comparator),
where anything that isn't the complete UUID would otherwise fail. Accept
strings as incomplete UUIDs for those scenarios.

* Enable type validation for all queries

https://greenkeeper.io/

http://greenkeeper.io/

* fix example

* use get method

* chore(package): update lodash to version 4.11.1

http://greenkeeper.io/

* chore(package): Work around issues with lodash.merge cloning

* Try to clarify adding and setting associations

Update associations.md

To support an alias for HasMany, the alias name must be specified in include, otherwise it will throw error like `unhandled rejection Error: Categories is not associated to Product!`

* Ignore model-level validation when creating join table for n:m associations.

When declaring a join table with the through option declared as a
string, Sequelize creates the through model at runtime, and copies the
model validation rules from the source table into the through model. More
often than not, the model validation rules from the source table would be
inappropriate/undesirable for the join table (since their data fields are
different anyway).

It's also worth noting that if a through model is given, this behavior
is not exhibited.

* Added unit test for issue #5556.

http://greenkeeper.io/

http://greenkeeper.io/

Add custom validation function testcases