Postgres: Timestamps are modified when saving other fields.

[wnortje]

When a timestamp field gets a value during record creation it also contains the microseconds

2015-09-23 13:28:49.562436

If the record is then read from the db via (single) and another field is changed and then the record is saved again, the timestamp field now contains this

2015-09-23 13:28:49

without the microseconds.

[eudoxia0]

I suppose this is a precision mismatch between local-time and Postgres. Is there a Postgres option for specifying the precision of timestamps?

[wnortje]

There may be a precision mismatch but I don't think that is what is causing the problem here. I think it is a conversion problem. Both the values I mention above are extracted from the table at different times.

The first value is created by local-time and stored in the DB. The change in accuracy happens when that records is read from the DB, modified and then saved

[intertricity]

I'm not entirely sure if this will help, but the postmodern site seemed to make a particular point about timestamps so I thought I'd relay it here- I was looking around for ORM's and this one looked really nice.

https://github.com/marijnh/Postmodern#caveats-and-to-dos