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
In general, our timestamp columns are of type timestamp(3) with time zone, where 3 is the precision value. However, entities."deletedAt" is timestamp without time zone: it differs on "with time zone" and also looks to have a precision value of 6. It looks like it's the only column like that and that other timestamp columns share the same type:
I can't think of an obvious way that these differences would have user-facing effects. For example, we don't filter on entities."deletedAt", so #459 isn't an issue. However, I think it'd be a good idea to make it the same type as other timestamp columns in case the differences lead to subtle issues.
The text was updated successfully, but these errors were encountered:
In general, our timestamp columns are of type
timestamp(3) with time zone
, where 3 is the precision value. However,entities."deletedAt"
istimestamp without time zone
: it differs on "with time zone" and also looks to have a precision value of 6. It looks like it's the only column like that and that other timestamp columns share the same type:I can't think of an obvious way that these differences would have user-facing effects. For example, we don't filter on
entities."deletedAt"
, so #459 isn't an issue. However, I think it'd be a good idea to make it the same type as other timestamp columns in case the differences lead to subtle issues.The text was updated successfully, but these errors were encountered: