This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-10-06
Channels
- # aleph (15)
- # announcements (2)
- # babashka (121)
- # beginners (62)
- # biff (6)
- # cherry (2)
- # cider (51)
- # clerk (30)
- # cljs-dev (5)
- # clojure (77)
- # clojure-austin (2)
- # clojure-europe (10)
- # clojure-germany (6)
- # clojure-nl (1)
- # clojure-norway (19)
- # clojure-romania (1)
- # clojure-uk (3)
- # clojurescript (16)
- # core-typed (7)
- # cursive (17)
- # datomic (12)
- # deps-new (11)
- # emacs (7)
- # events (2)
- # fulcro (5)
- # honeysql (2)
- # hyperfiddle (32)
- # introduce-yourself (1)
- # jobs-discuss (2)
- # membrane (18)
- # missionary (2)
- # music (5)
- # polylith (7)
- # reagent (26)
- # releases (5)
- # testing (32)
- # tools-build (14)
- # tools-deps (7)
- # xtdb (8)
We are wondering if a call to xt/submit-tx
always results in a new transaction log entry, even if it is an empty transaction. Does it?
Hey @U029CG5DAPP - yes it will do, and you can observe this by noting how the returned tx-id and tx-time are increasing
Okay, thanks for the information π We have a background process that transacts every few minutes, so we will ensure then that it only calls tx/submit-tx
when there actually is something to transact, so we don't pollute the log.
is there an xt/entity-tx
for multiple eids? I have a sequence of eids I'd like to get the ::xt/tx-time
for...
Even better if I can do it via a single query...
Hey @U0HJD63RN you can call xtdb.api/entity-tx
from within a query, e.g.
{:find [etx]
:in [[e ...]]
:where [[(xtdb.api/entity-tx $ e) etx]]}