You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Do we need to add a check for inserted_at and updated_at and if yes do we want to check that the type of these value is naive_datetime_usec to make sure that microseconds are saved in Postgres?
👍 Timestamps are necessary so we probably should require them the same way.
I don't think it's necessary that the type be naive_datetime_usec though. The timestamps are used to ensure we're fetching the most recent update of an item, and I don't think it's likely that two relevant updates would be performed within microseconds of each other. Saying that though, it would provide more of a guarantee of correct data, so maybe we should recommend it rather than require it.
alog is checking that the schemas of the application have the minimum fields defined to allow the package to work:
alog/lib/alog.ex
Line 68 in 4cbf9d7
alog/lib/alog.ex
Line 79 in 4cbf9d7
However it doesn't check that timestamps are defined.
timestamps are used in the queries to make sure to retrieve the correct item:
alog/lib/alog.ex
Lines 106 to 114 in 4cbf9d7
Do we need to add a check for
inserted_at
andupdated_at
and if yes do we want to check that the type of these value isnaive_datetime_usec
to make sure that microseconds are saved in Postgres?see https://hexdocs.pm/ecto/Ecto.Schema.html#module-the-datetime-types
The text was updated successfully, but these errors were encountered: