WIP
implement object "attribute" (aka fields) property getters/setters on DAOs such that custom object property getter/setter functions can be applied to a DAO instance (not yet implemented, but I suspect in to be defined along-side "instanceMethods"), all attribute values ar enow stored in a "dataValues" property and transparently made available for setting and getting via object property get/set functions
add tests for getters/setters, bugfix, refactor - its WIP
remove property check in DAO.prototype.setDataValue - it is not correct and causes an infinite loop when setting a data value for a field that is as yet unset (via a property setter that has the same name as the original property)
Updated config directory to correct location in examples.
* other line changes are whitespace trims (auto by ide)
Updated readme with runnable examples
updating generic-pool version (to include validate functionality)
Adding connection validation and handling of PROTOCOL_CONNECTION_LOST errors
node domains supported
merge sequelize@1.7.0-alpha1 - trying to keep the PR up2date
Merge package.json
make it possible to define property getter and setter functions in a data attribute definition (by defining a "get" and/or "set" property) ... these take preference to getters/setters defined (for an attribute of the given name) in the options object - some buster tests included
bogus commit (no code changes) to force travis-ci to run again (lets hope there are no timeouts in the postgres test run this time :-/
Add promise then to custom emitter
"getWhereConditions" in the postgres "QueryGenerator"
can now prepend table names to attributes. This fixes
issue #629.
Fixed two syntax errors in postgres QueryGenerator (removed 2 unneeded commas).
Updated postgres query-generator jasmine spec to
make changes in issue #629 pass.
Merge pull request #630 from Obbedire/master

Issue #629: Attribute ambiguity issue when eagerly loading.
Run tests for 0.10 as well
PG does not like v0.10. Update buster dep. to 0.6.3