Unable to load version using ActiveRecord updated_at

[jasonjho]

If I understood the docs, the timestamp is derived from the updated_at timestamp at the record level. In my case, I have these set by ActiveRecord, so they are always available.

If I try to load a version at(time: <record.updated_at>), I am getting back nil. Somehow, the timestamps seem to be off by 1 millisecond after inspecting log_data. Simply adding 1 to the timestamp will yield the expected result, but I feel I am missing something here.

I simply want to grab the version based on the recorded updated_time. Any tips would be appreciated, thanks!

[jasonjho]

It seems as if the trigger function is rounding up somehow and storing that in ts.

[palkan]

Sorry for a long reply.

the timestamp is derived from the updated_at timestamp at the record level

That's only true if you have provided the timestamp_column to the logidze:model generator. How does your Logidze migration for the table look like?

[jasonjho]

We have an updated_at column already present on the entity table. Based on the docs, I thought logidze would attempt to always use this as the default strategy, otherwise defaulting to the statement ts.

I see the following in our sql trigger. Does this mean we have the right setting?

EXECUTE PROCEDURE logidze_logger(null, 'updated_at');

[palkan]

Does this mean we have the right setting?

Yep, looks good.

Could you, please, provide an example of SQL rows with wrong timestamps?