Jan Aagaard Meier
Jan Aagaard Meier
@ssteffl you can do `instance.changed('updatedAt', true)`
The workaround you showed could prettymuch verbatim be added to the pg connection manager :) The only change would be that it should use `this.sequelize.options.timezone` (https://github.com/sequelize/sequelize/blob/master/lib/dialects/mysql/connection-manager.js#L31) instead of always Z
@chris-33 Are you up for providing a PR? As I said, this should be a pretty easy fix, you've already found the right way to fix this, so it just...
@zaptree You are right about the fix mentioned here only working for UTC - that's why I mentioned `options.timezone` previously. Your diagnosis of the problem is correct - the problem...
``` js user.set('id', 42, { raw: true }); user.changed('id', true); ```
@danielo515 any recent version I think. The only thing missing in the example I posted is to call save
Just tested this again, and I discovered a problem - updating the primary key also updates the where clause (`SET "id"=44 WHERE "id" = 44`) You should use bulk update...
In general sequelize doesn't have great support for composite primary keys, so I think I would recommend using a bulk update
You should be able to this though: ``` js User.update({ clicks: sequelize.literal('clicks +1') ,... ) ```
@hebbian You have to give some more context than that if you want us to help you - What code are you running, and what does the query look like...