public / sequelize

…perty in terms of getters and setters, we should not care about whether the relevant underlying dataValue is already set or not - previously added/initialized properties may have setters that set the dataValue of the attribute currently being added/initialized (e.g. the setter of a "name" property that also sets the dataValue for the "slug" property, when the "slug" property is defined after the "name" property, in the model,and the bogus sanity check in place the "slug" property does not get its setters/getters defined ... thereby breaking the model!)

…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

Keep milliseconds in timestamps for postgres

Bumped pg to 2.0.0

Use moment for better postgres timestamp strings

Fix for many-to-many associations being impossible between models with custom table names

Fix quotation escape in postgres where conditions

Fix HSTORE encoding by using pg-hstore library.

… (removes errors about the use of reserved keywords

hasMany setter uses bulk create and destroy to create and remove associations

Fixes #644