This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2015-10-23
Channels
- # announcements (1)
- # aws (11)
- # beginners (28)
- # boot (235)
- # business (1)
- # cider (19)
- # clojure (34)
- # clojure-china (1)
- # clojure-czech (10)
- # clojure-japan (7)
- # clojure-poland (3)
- # clojure-russia (84)
- # clojure-sg (4)
- # clojure-uk (3)
- # clojurescript (114)
- # community-development (4)
- # core-async (15)
- # cursive (8)
- # datascript (5)
- # datomic (6)
- # editors-rus (27)
- # events (2)
- # hoplon (61)
- # jobs (2)
- # ldnclj (56)
- # ldnproclodo (5)
- # lein-figwheel (232)
- # luminus (1)
- # off-topic (5)
- # om (215)
- # onyx (436)
- # overtone (8)
- # re-frame (3)
- # reagent (3)
Is there any harm in putting enum values in :db.part/db
instead of :db.part/user
as the docs show?
Is it possible to create a transaction that contains a circular reference? I'm trying to install an attribute and annotate a transaction with that attribute at the same time but it's erroring. https://gist.github.com/DomKM/fda80d4d3e948ae31140
pretty sure that’s not possible, @domkm - it uses the known-good schema to validate the transaction, the in-flight tx is not known-good at that point
enums in db, what happens when you try – does it work?
@robert-stuttaford: Re: enums in :db.part/db
, I haven't tried but I assume it would work. However, I'm also able to (if memory serves) create an attr that begins with :db.
which is explicitly disallowed, so I think there's not much validation.