This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2015-10-06
Channels
- # admin-announcements (2)
- # aws (3)
- # beginners (25)
- # boot (7)
- # cider (27)
- # cljs-dev (30)
- # clojure (106)
- # clojure-boston (1)
- # clojure-czech (3)
- # clojure-dev (3)
- # clojure-estonia (1)
- # clojure-italy (1)
- # clojure-russia (11)
- # clojure-uk (3)
- # clojurescript (83)
- # clojurex (1)
- # datascript (1)
- # datomic (21)
- # docs (7)
- # funcool (1)
- # hoplon (8)
- # jobs (2)
- # ldnclj (9)
- # leiningen (6)
- # om (6)
- # onyx (29)
- # re-frame (41)
- # reagent (64)
- # spacemacs (2)
- # test200 (1)
So I've been thinking about datascript persistence, and I came across this: https://gitter.im/tonsky/datascript/archives/2015/03/28, which turned me on to the idea of actually storing eavt instead of the serializing the whole db and storing it as a string, which is what I'm doing now. (the db in question is not large). But, I struggle a bit with how this actually works on the query side. Is there some resource I can learn from about this? Or does, eg. a Datomic peer, just grab every datom for, a given entity, and then sort by a, v, t to get current values?