How to update 'updatedAt' column in bulk update?

[alekbarszczewski]

Using master version.

User.update({ field1: 'val1' },{ type: 'admin' }).done(...)
User.update({ field1: 'val1', updatedAt: new Date() },{ type: 'admin' }).done(...)

In both cases updatedAt column is ignored (it does not appear in SQL SET statement).

[mickhansen]

Strange that it is ignored in the second statement.
Not sure if this is because it's parsing the values through individual instances where they ignore read only attributes.

[seth-admittedly]

I'm seeing the same problem with bulkCreate and the created_at attribute.

[janmeier]

@mickhansen , yep the validation and instance creation is the issue, read only attributes are skipped.

A simple fix is adding raw: true to https://github.com/sequelize/sequelize/blob/master/lib/model.js#L1375. But then setters will not be called? Is that expected behaviour for bulk?

edit did a quick check - all tests pass when adding raw: true

[mickhansen]

@janmeier i assume people would expect bulkCreate to work with setters and defaultValues etc so. We might not have tests for that though.

[janmeier]

Hmm yeah - so we should have an option that uses setters / getters, but also allows you to set read only attrs

[mickhansen]

Or we implement the updatedAt/createdAt logic ourselves in bulk create/update.

[janmeier]

@seth-admittedly Can't reproduce for bulkCreate on latest master - mind providing a test case?