This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-04-02
Channels
- # asami (5)
- # aws (16)
- # babashka (41)
- # babashka-sci-dev (44)
- # beginners (157)
- # biff (3)
- # cider (1)
- # clj-commons (1)
- # cljdoc (22)
- # clojure (7)
- # clojure-dev (5)
- # clojure-europe (13)
- # clojure-nl (1)
- # clojure-uk (1)
- # clojurescript (17)
- # core-typed (13)
- # cursive (14)
- # datascript (10)
- # events (1)
- # fulcro (2)
- # graalvm (2)
- # gratitude (1)
- # jobs (3)
- # lsp (229)
- # pathom (2)
- # pedestal (3)
- # portal (53)
- # re-frame (7)
- # remote-jobs (1)
- # spacemacs (14)
- # xtdb (6)
Hi! If I transact {:tx-data [{:db/id -1, :name "first"}, {:db/id -2, :account-balance-usd -1}]} then the second entity's :account-balance-usd will end up pointing to the first entity instead of holding the expected value -1 . I guess that the only way to avoid it is to make sure that the temp id values differ from values used in attributes, right?
For now… yes. I know this is a problem, and knew it when I did it. But it also didn’t hit any of my use cases, and I thought that maybe I’d get away with it 😳
I have a few ways to avoid this. I can use node refs, or I can use schemas (which are coming). But I have yet to implement either
No problem! There is an OK solution. I don't complain, Asami is a great p piece of SW and you put a lot of effort into it. As long as I know what (not) to do, it's perfectly fine :)