Notice: All 1.7.x changes are present in 2.0.x aswell
# Next
-[FEATURE] Added to option of setting a timezone offset in the sequelize constructor (`timezone` option). This timezone is used when initializing a connection (using `SET TIME ZONE` or equivalent), and when converting a timestamp string from the DB to a JS date with mysql (postgres stores the timezone, so for postgres we rely on what's in the DB).
# v2.0.0-dev12
-[FEATURE] You can now return a promise to a hook rather than use a callback
-[FEATURE] There is now basic support for assigning a field name to an attribute `name: {type: DataTypes.STRING, field: 'full_name'}`
...
...
@@ -12,7 +16,6 @@ Notice: All 1.7.x changes are present in 2.0.x aswell
-[FEATURE] Extract CLI into [separate projects](https://github.com/sequelize/cli).
-[FEATURE] Sqlite now inserts dates with millisecond precision
-[FEATURE] Sequelize.VIRTUAL datatype which provides regular attribute functionality (set, get, etc) but never persists to database.
-[FEATURE] Added to option of setting a timezone offset in the sequelize constructor (`timezone` option). This timezone is used when initializing a connection (using `SET TIME ZONE` or equivalent), and when converting a timestamp string from the DB to a JS date with mysql (postgres stores the timezone, so for postgres we rely on what's in the DB).
-[BUG] An error is now thrown if an association would create a naming conflict between the association and the foreign key when doing eager loading. Closes [#1272](https://github.com/sequelize/sequelize/issues/1272)
-[BUG] Fix logging options for sequelize.sync
-[BUG] find no longer applies limit: 1 if querying on a primary key, should fix a lot of subquery issues.
