change use of doa.value property to using doa.dataValues
when we validate - just do it on the contained dataValues, and lets actually check 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)
fix a test - bad model property name used, namely "name" when it should have been "username" (note that this broken test has nothing to do with the changes in this branch :-/)
fix failing test related to SQL generated for bulk insertions - the SQL was correct 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)