public / sequelize

http://greenkeeper.io/

Hooks Tests and Refractor

Execute promises sequentially rather than parallel

Fix DELETE WHERE 1=1 when complex objects passed in options.where to destroy or update

Promise.map allows promises to execute in parallel, which can cause
deadlocks when cascading truncates. Promise.each executes promises
sequentially, which should ensure that we don't have two or more
TRUNCATE operations getting in each others' way.

Fix bug in SqlString.escape which caused the function to be recursive…

…ith the wrong parameters when passed an array of strings. This would cause the incorrect escape algorithm to be used on the strings within the array when the dialect was set to postgres, sqlite, or mssql.

…github.com/sequelize/sequelize/issues/5496

bluebird@3.3.2

http://greenkeeper.io/

Support querying the through model

[ci skip] Added Sequelize.DATEONLY to docs

Fix issue with undefined column having defaultvalue

…Inf) in pg and sqlite. Closes #5194

Added validationFailed hook

add a beforeCount hook

Added locales support for localized validations

Log which query tried to run on a finished transaction

empty array  in where should return no data

Update generic-pool to version 2.4.1 🚀

http://greenkeeper.io/

The "commit has been called on this transaction" error message usually indicates a problem with chaining of query promises within a transaction block. In more complex transaction blocks it may not be immediately clear which query is improperly chained and the current error message does not help much. This change attaches the rejected query (SQL) as the 'sql' property of the error. This makes it easier to identify a problem in an application.