This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-02-03
Channels
- # beginners (48)
- # boot (26)
- # cider (7)
- # cljsrn (1)
- # clojure (137)
- # clojure-nl (1)
- # clojure-spec (5)
- # clojure-uk (18)
- # clojurescript (26)
- # cursive (8)
- # datascript (4)
- # datomic (4)
- # defnpodcast (11)
- # docker (1)
- # duct (7)
- # figwheel (4)
- # fulcro (7)
- # off-topic (7)
- # re-frame (46)
- # reagent (40)
- # reitit (3)
- # shadow-cljs (4)
@marshall “The Schema Growth principle provides a means for entites” https://docs.datomic.com/on-prem/best-practices.html
@marshall / @stuarthalloway you may want to drop the note about using squuid on the best practice doc, given that adaptive indexing makes it redundant and Client doesn’t expose it
@alex438 The Datom itself does not have a time information but references the Transaction which records the transaction time (:db/txInstant). The transaction time provides a reference point for the state of the world from the perspective of the database (used as “aggregate all datoms from the beginning of time up to the transaction time”). I keep that completely separate from other notions of time in my business domain. In my business domain I want to answer questions like “When was Alice born?” not “When became Datomic aware of the fact that Alice was born on …“; a subtle but important distinction.