This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-08-29
Channels
- # admin-announcements (2)
- # beginners (20)
- # boot (139)
- # cider (6)
- # clara (1)
- # cljs-dev (7)
- # cljsrn (4)
- # clojure (160)
- # clojure-berlin (1)
- # clojure-canada (6)
- # clojure-gamedev (1)
- # clojure-japan (7)
- # clojure-russia (14)
- # clojure-spec (90)
- # clojure-uk (10)
- # clojurescript (73)
- # clojutre (1)
- # conf-proposals (8)
- # crypto (67)
- # cursive (9)
- # datomic (6)
- # editors-rus (1)
- # events (1)
- # figwheel (6)
- # funcool (2)
- # hoplon (19)
- # instaparse (37)
- # kekkonen (4)
- # lein-figwheel (2)
- # leiningen (5)
- # luminus (1)
- # off-topic (1)
- # om (10)
- # onyx (60)
- # protorepl (2)
- # re-frame (81)
- # reagent (10)
- # ring-swagger (15)
- # rum (6)
- # specter (17)
- # test-check (10)
- # uncomplicate (31)
- # untangled (12)
- # yada (6)
@magnars t starts at 1000 and tx starts from 13194139534312, 10 billion datoms is Datomic's reccomended limit
@danielstockton @magnars In fact the 10B recommendation doesn’t stem from tx or t numbers, but rather from logistical size considerations for DBs that large (i.e. restore from backup of that size can take hours or days depending on infrastructure)
i know, i just interpreted magnars question as "when as-of takes a number, how does datomic know whether it represents a T or a tx" and i presumed the id ranges are far enough apart for them never to overlap
@marshall, and also the amount of ram that holding all the roots and idents and whatnot would use, right?