This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2024-07-10
Channels
- # announcements (1)
- # babashka (17)
- # biff (7)
- # calva (6)
- # clerk (5)
- # clj-on-windows (1)
- # clojure (59)
- # clojure-austin (17)
- # clojure-brasil (1)
- # clojure-europe (40)
- # clojure-nl (2)
- # clojure-norway (103)
- # clojure-sweden (9)
- # clojure-uk (8)
- # clojurescript (8)
- # cursive (25)
- # data-science (5)
- # datalevin (7)
- # datomic (4)
- # emacs (8)
- # etaoin (13)
- # hyperfiddle (26)
- # lsp (8)
- # malli (7)
- # off-topic (9)
- # polylith (13)
- # releases (2)
- # sql (7)
Hello! If I have a list of numbered entities, [{:e/id 0} {:e/id 1} ,,,]
, transact it in (in a single transaction), will the :db/id's maintain the same sort-order as my own :e/id ?
I'm asking because I'm shuffling a list of entities before transacting it in, and I suspect they're coming out in a less random order (which perhaps I can "fix" by sorting by :db/id)
Thanks for the confirmation! And all your hard work 🙂
One more thing — am I right in thinking that unlike other Datomic-likes, DL entities can be arbitrarily modified & transacted back in?! Something on github seems to imply they keep a "staging area" of changes, to make this efficient for modified data at arbitrary depths. Can I use them wherever I'd use a map, like (transact! conn [{:new-thing/ref my-entity}])
?
My current code is littered with messy pull-specs, and I'm passing around maps with various "bits" hanging off, making it feel awkwardly coupled all over the place.
Yes, DL entity is transactable. Please see https://cljdoc.org/d/datalevin/datalevin/0.9.8/doc/transaction#transactable-entities-in-datalog-store