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 Postgres, we actually have several time/date datatypes, and this is very useful feature which provide clear modeling of the user domain. However, if Plenish always directly map Datomic timestamp to Postgres timestamp, we can not leverage these Postgres features.
Possible Solution:
have some additional configuration for Plenish regarding column types. Now we see "oh this is :db.type/inst", so we make a postgresql timestamp (same semantics), but the use could configure that this needs to become an SQL DATE column instead, and set up some kind of coercion
The text was updated successfully, but these errors were encountered:
Problem
In Postgres, we actually have several time/date datatypes, and this is very useful feature which provide clear modeling of the user domain. However, if Plenish always directly map Datomic timestamp to Postgres timestamp, we can not leverage these Postgres features.
Possible Solution:
have some additional configuration for Plenish regarding column types. Now we see "oh this is :db.type/inst", so we make a postgresql timestamp (same semantics), but the use could configure that this needs to become an SQL DATE column instead, and set up some kind of coercion
The text was updated successfully, but these errors were encountered: