This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-09-03
Channels
- # announcements (3)
- # beginners (114)
- # calva (42)
- # cider (90)
- # clj-kondo (3)
- # cljsrn (6)
- # clojure (40)
- # clojure-conj (4)
- # clojure-dev (3)
- # clojure-europe (4)
- # clojure-italy (3)
- # clojure-nl (4)
- # clojure-quebec (1)
- # clojure-spec (3)
- # clojure-uk (130)
- # clojurescript (31)
- # cursive (3)
- # data-science (3)
- # datavis (1)
- # datomic (5)
- # dirac (3)
- # fulcro (16)
- # jobs (1)
- # joker (6)
- # music (5)
- # off-topic (14)
- # re-frame (19)
- # remote-jobs (8)
- # shadow-cljs (37)
- # slack-help (4)
- # tools-deps (22)
- # xtdb (8)
I've streamlined the docs - any feedback appreciated. https://juxt.pro/crux/docs/index.html
are references between documents supported in Crux? IIUC it doesn't enforce schema nor referential integrity, and is designed as a document-oriented database so you are expected to store collections of documents instead of a graph of entities, is that correct?
Hi @UJDDXBY80! References are dynamically resolved during the query execution, which means there's no need to declare upfront which attributes are reference types. As long as the value is a valid :crux.db/id then the query will navigate the relationship just fine. You can even store those IDs in a vector or set (which is effectively like cardinality)