public / sequelize

Update copyright year range to 2015

…es trigger a unique error

For cases where the primary `where` passed to findOrCreate does not trigger a unique error but the default values does the code would then attempt a find on the were resulting in the perceived impossible return value of [null, true]

…a noop rather than an empty query

Sequelize tries to optimize which fields are being updated by
checking previous data values, and determining whether or not
fields should be used in an UPDATE clause. Unfortunately, the
case where NO fields should be used in the clause was never
checked.

refactor(mysql/enum): remove support for ci enums in mysql

Update migrations.md

Added a line about using the command line when CLI is installed locally

Throw an error if no where clause is given to Model.destroy()

Add instanceof check to error

Update changelog