public / sequelize

Only for rawSelects it seems that Sequelize forcibly adds timezone
information to dates returned from the database. This breaks in
strange and magical ways

add default implementation for upsertQuery

Some dialects developers might need to be reminded they need to
implement the upsertQuery.

fix schema test and move dropSchema to AbstractDialect

The schema.test.js added yesterday was using before/after in the
test cases when this.sequelize was not guaranteed to be present yet.
This also moves dropSchema to the AbstractDialect, currently the
code simply assumed you had this implemented in your dialect

Fix findAndCountAll with include all

…utely required includes

add ability to determine dialect migration support

This provides the ability to determine whether a given dialect
is supported for migrations. This is mostly another switch that
allows incremental implementation of new dialects.

remove node-sql and query generation syntactic sugar

This is an incomplete feature that seems to be unused by the user
base. Furthermore, it does not support incoming dialects (notably
MSSQL), and thus has been slated for removal for the 2.0 release

Fix allowNull in combination with primaryKey

…ield prop after create, fixes #2468

Fix increment and decrement usage with schemata

…/sequelize into vpontis-associating-sections-when-deletions

…result in a promise chain

add ability to test for dialect transaction support

…nd attributes as fields

Transaction support is currently very limited in the MSSQL dialect,
this allows us to conditionally skip transaction related tests for
a given dialect. I imagine it's also a nice feature to have when
adding a new dialect, so you don't have to solve all one thousand
errors at the same time