This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-11-29
Channels
- # adventofcode (7)
- # announcements (11)
- # beginners (76)
- # boot (3)
- # calva (139)
- # cider (24)
- # clara (2)
- # cljdoc (11)
- # cljs-dev (90)
- # cljsjs (1)
- # cljsrn (3)
- # clojure (98)
- # clojure-austin (2)
- # clojure-brasil (2)
- # clojure-dev (16)
- # clojure-europe (3)
- # clojure-italy (55)
- # clojure-nl (37)
- # clojure-sweden (11)
- # clojure-uk (40)
- # clojurebridge (1)
- # clojurescript (107)
- # core-logic (10)
- # cursive (34)
- # data-science (9)
- # datascript (19)
- # datomic (48)
- # emacs (6)
- # figwheel (13)
- # figwheel-main (3)
- # fulcro (67)
- # jobs (1)
- # juxt (4)
- # lumo (8)
- # mount (1)
- # off-topic (29)
- # onyx (1)
- # reagent (7)
- # reitit (3)
- # ring-swagger (5)
- # shadow-cljs (39)
- # spacemacs (5)
- # tools-deps (1)
hey folks, I'm a bit confused about datascript indexes. is it actually store all the datums in the index nodes ?
Yes @lxsameer. Not only that, it stores them all at least 3 times because there are 3+ indexes.
It might be at least 2 times, need to refresh my memory
http://tonsky.me/blog/datascript-internals/ might be interesting to you
First time i'm hearing of it, but I'm familiar with 'hitchiker trees'
cool, so it does not make sense to me to store the data in the B+ or hitchhiker tree index nodes 3 times
No, I bet its the same in datahike. Datomic also stores the atoms in the index nodes, multiple times.
It's a trade off between storage (cheap) and performance