lambdaisland / lambdaisland/plenish
Datomic doesn't have a `date` type, it only has a `timestamp` type.
Nobody has claimed this yet.
- Dominant language
- Clojure
- Stars
- 56
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
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
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the mapping from Datomic :db.type/inst to PostgreSQL timestamp and the configuration entry points for column types. Review how coercion is currently handled, then define the supported configuration, date semantics, and tests needed to show that an inst can become an SQL DATE column.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clojure, postgresql
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100