This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-02-18
Channels
- # beginners (56)
- # boot (1)
- # cider (96)
- # cljs-dev (148)
- # clojure (60)
- # clojure-austin (11)
- # clojure-france (2)
- # clojure-italy (5)
- # clojure-russia (11)
- # clojure-spec (31)
- # clojure-uk (5)
- # clojurescript (52)
- # community-development (37)
- # cursive (3)
- # data-science (8)
- # datomic (14)
- # devcards (2)
- # emacs (1)
- # fulcro (13)
- # hoplon (1)
- # immutant (2)
- # luminus (3)
- # off-topic (2)
- # onyx (16)
- # parinfer (38)
- # re-frame (8)
- # reagent (5)
- # shadow-cljs (332)
- # spacemacs (5)
- # specter (5)
- # sql (6)
- # vim (52)
should enum refs be isComponent
or not?
I answered my own question at a REPL
they should not be
Should this be called out in the docs? I just spent many frustrating hours trying to figure out why my data was disappearing b/c of this confusion.
Rule of thumb for isComponent: an entity referenced by an isComponent attr should only be referenced once in the whole db
If your data model requires multiple refs it is very likely the attr should not be isComponent
I don’t really get the pricing... too much fine print on the official Amazon pricing page https://aws.amazon.com/marketplace/pp/prodview-otb76awcrb7aa
Anyone care to comment about storage and networking costs which are incurred by their usage? Clearly a bit hard to guess how much my data would consume in Datomic storage...
hi @matan — see https://forum.datomic.com/t/datomic-cloud-pricing-fully-loaded-cost/306/4
@stuarthalloway thank for the link! :-) now it only remains how much “domination” is there as the data grows and the number of instances remains constant ;-)