public / sequelize

…s to make sure that we're getting the right information back.

…to ActiveRecord's scope. 2. Big internal changes (but as of right now only related to scope()) made for the {where} object when using finders. Could be useful for some, it basically breaks down several where objects into one concise object. 3. New where finders.. 'eq', 'like', 'nlike', 'notlike', and 'not' (not in). 4. New finder shortcuts, '..' for between and '..' for not between

Closes #723 (consistent handling of limit and offset across dialects)

Added basic where logic to sequelize closes #321

Cleaned up configuration.spec.js and made Sequelize throw an error for a dialect that doesn't exist. Closes #729.

… that doesn't exist. Closes #729.

Make explicit migrations possible.

Better BigInt support for PostgreSQL.

Bugfix for the problems related to eager loading associations and subsequent saving of DAO instances

implement "sugar" wrapper method for findAll() followed by count()

Made better error messages for when we have trouble connecting to a database. Closes #227

PostgreSQL should now be able to insert empty arrays with typecasting. Closes #714

Fields should be escaped by quoteIdentifier for max/min functions which allows SQL reserved keywords to be used. Closes #676

Identity comparison for bigint

…QL reserved keywords to be used. Closes #676

…ect but the test assumed that the fields were specified in a different order (I think switching from `doa.values` to `dao.dataValues` affected the order of field names in generated SQL)

…n "username" (note that this broken test has nothing to do with the changes in this branch :-/)

…ck that we have a rawAttribute definition for each value we attempt to validate (seems that it is possible to set stuff into a doa instance even though the model does not know about a given property)

Added the ability to tell Sequelize what language to go by for singular/plural functions. Closes #683