This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-08-02
Channels
- # announcements (3)
- # beginners (28)
- # calva (5)
- # clj-kondo (17)
- # cljsrn (1)
- # clojure (69)
- # clojure-dev (23)
- # clojure-europe (1)
- # clojure-italy (27)
- # clojure-japan (1)
- # clojure-nl (5)
- # clojure-spec (34)
- # clojure-uk (87)
- # cursive (93)
- # datomic (15)
- # duct (6)
- # emacs (3)
- # events (2)
- # garden (1)
- # graalvm (4)
- # jobs (3)
- # malli (1)
- # off-topic (13)
- # onyx (1)
- # pathom (8)
- # pedestal (2)
- # re-frame (13)
- # reitit (5)
- # shadow-cljs (13)
- # sql (13)
- # test-check (5)
- # testing (3)
- # yada (1)
Is the “single parent” policy implied by isComponent true
attributes enforced by datomic? It seems like I can add another parent to a child, and then the backref behavior is really strange
here’s what i’m seeing (both asserts pass)
Yes, you can
If :foo/bar
isComponent and you insert [2 :foo/bar 1]
and [3 :foo/bar 1]
- if you retractEntity 3, 1 will be retracted
- if you retractEntity 2, 1 will be retracted
- in pull/entity API if you ask for for :foo/_bar
from 1
, it will return just 2
or just 3
"randomly"
- in query, it should not effect
thanks @souenzzo 🙂, that’s exactly what I’m seeing but the semantics were just confusing at first
yeah, having a “consistent view” of the db and a backref that is “random” doesn’t exactly jive
just have to add more validation to my txns to ensure ever child only has one parent
stable for a given value of db?
until a reindex or something?
Does anyone know if datomi.api/gc-storage
collects just on the database specified in the connection or across all databases in the Datomic deployment?
https://docs.datomic.com/on-prem/clojure/index.html#datomic.api/gc-storage
Can someone tell me why the above wouldn’t work?