This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2015-11-23
Channels
- # admin-announcements (38)
- # announcements (1)
- # aws (1)
- # beginners (195)
- # boot (1)
- # business (3)
- # cider (100)
- # cljsrn (37)
- # clojure (99)
- # clojure-russia (69)
- # clojure-switzerland (1)
- # clojurescript (120)
- # datavis (26)
- # datomic (23)
- # devcards (4)
- # editors (38)
- # hoplon (18)
- # ldnclj (27)
- # lein-figwheel (28)
- # off-topic (50)
- # om (329)
- # onyx (255)
- # portland-or (1)
- # re-frame (8)
- # reagent (18)
- # spacemacs (5)
- # testing (1)
I transact a single, large transaction (10,000s of txs), but datomic reports :db.error/tempid-not-an-entity tempid used only as value in transaction
. Is there a way to see which tempid is failing the transaction?
I looked at transactor logs (with log level :debug), but it doesn't print the culprit
you have a tempid with no attr/values assigned
something like {:db/id (d/tempid :db.part/user)}
(shooting from the hip here, i admit )
I'm using only the [:db/add e a v]
form
My assumption is that this error means that I'm using a tempid as a value but not (in the same tx-data) also as an entity
ah, yes
still working on the EDN exporter btw
almost there.. except for this pesky bug
a tempid needs to appear at least once in E position
you likely have a ref to a tempid without actually giving that tempid some data
right
that's the thing -- if I read my tx-data correctly, I've removed all those instance
you should be able to write some scratch code to find all tempids in V position and validate that they all appear in E position at least once
also - are all your enums included in your dataset?
[:db/add (tempid) :db/ident :status/awesome]
these guys
gotta run. good luck!
thanks, very helpful
Questions for Cognitects: I'm building a type system on top of Datomic and have encountered a few anomalies. Why aren't functions installed with db.install/function
(`:db.fn/cas` and :db.fn/retractEntity
are values of :db.install/function
)? What is :db.bootstrap/part
? It's not referenced by any other entities. It looks like an artifact of DB bootstrap process that should maybe be retracted. CC @bkamphaus
Spec-tacular something with types.