This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-08-11
Channels
- # architecture (11)
- # bangalore-clj (1)
- # beginners (42)
- # boot (28)
- # chestnut (1)
- # cider (1)
- # cljs-dev (28)
- # cljsrn (7)
- # clojure (124)
- # clojure-austin (1)
- # clojure-italy (10)
- # clojure-russia (3)
- # clojure-spec (29)
- # clojure-uk (32)
- # clojurescript (62)
- # core-async (22)
- # data-science (7)
- # datascript (5)
- # datomic (8)
- # events (1)
- # fulcro (15)
- # funcool (1)
- # jobs (1)
- # keechma (10)
- # lein-figwheel (4)
- # lumo (4)
- # mental-health (1)
- # off-topic (21)
- # om (10)
- # onyx (8)
- # parinfer (29)
- # pedestal (1)
- # planck (4)
- # portkey (2)
- # protorepl (1)
- # random (1)
- # re-frame (12)
- # ring (3)
- # spacemacs (6)
- # uncomplicate (63)
is there any way to tell apart the datoms in :tx-data that were transacted by the user versus ones that were tacked on like the transaction datum, and in some cases :db.alter/attribute datums?
@uwo http://docs.datomic.com/transactions.html#making-temporary-ids The transaction datom is in a different partition, as are schema datoms
@marshall thanks. I did notice that. Are the only other generated datoms db.atler and db.install (ignoring the retracts that are implicit in an update)
I found the problem, I need to add (:db-after db) instead of only db!