Fork me on GitHub
#datomic
<
2018-02-18
>
cap10morgan02:02:12

should enum refs be isComponent or not?

cap10morgan02:02:07

I answered my own question at a REPL

cap10morgan02:02:13

they should not be

cap10morgan02:02:55

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.

favila04:02:19

Rule of thumb for isComponent: an entity referenced by an isComponent attr should only be referenced once in the whole db

favila04:02:15

If your data model requires multiple refs it is very likely the attr should not be isComponent

favila04:02:23

(Referenced once means (d/datoms db :vaet the-entity) is count = 1)

matan11:02:24

Hi, is this also a good place to ask about Datomic cloud?

matan11:02:59

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

matan11:02:08

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...

matan11:02:18

In terms of the Datomic overhead and such

matan16:02:09

@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 ;-)

matan16:02:26

Is there any orthogonal community channel dedicated specifically to Datomic cloud?