This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-10-22
Channels
- # announcements (9)
- # asami (52)
- # aws (1)
- # babashka (7)
- # babashka-sci-dev (12)
- # beginners (72)
- # calva (24)
- # cider (9)
- # clj-kondo (76)
- # cljs-dev (15)
- # clojure (19)
- # clojure-australia (4)
- # clojure-europe (33)
- # clojure-france (9)
- # clojure-gamedev (17)
- # clojure-nl (6)
- # clojure-portugal (5)
- # clojure-uk (5)
- # clojurescript (61)
- # clojureverse-ops (4)
- # code-reviews (23)
- # conjure (1)
- # data-science (2)
- # datalevin (6)
- # datomic (49)
- # gratitude (1)
- # helix (24)
- # holy-lambda (14)
- # jobs (3)
- # lsp (92)
- # malli (7)
- # missionary (8)
- # pathom (12)
- # proletarian (3)
- # re-frame (4)
- # remote-jobs (1)
- # shadow-cljs (4)
- # spacemacs (3)
- # sql (9)
- # tools-build (90)
- # vim (1)
- # xtdb (11)
FYI https://xtdb.com/blog/dev-diary-aug-21.html returns 404 and "An Error Occurred While Attempting to Retrieve a Custom Error Document"
Hmm. This URL does work https://xtdb.com/blog/dev-diary-aug-21/, so looks like we need to fix the routing with a redirect potentially.
> Some major changes to the site happening yesterday ...and continuing for a while, which is why we haven't announced the new website yet. 😉 @holyjak Thanks for the heads-up. 🙏 Some 302s are emerging as we speak.
Apologies for any website clumsiness, folks. This is quite a substantial overhaul under the hood, partly in preparation for next year's 2.x series of XTDB.
Is is it possible to query the transaction log? Was thinking of something like
(xt/q (xt/db node) '{:find [(pull ?tx [*])]
:where [[?tx :xtdb.api/tx-id]]})
I am mainly interested in getting all the info for certain transaction ids. I don't know if transactions are even first class entities so maybe this doesn't make much sense.> I don't know if transactions are even first class entities
In XT they're not. You would need to reify them yourself, which can be done in userspace (although to capture the tx-id you'd need a transaction function)
Have you looked at the open-tx-log
API already? What are you trying to achieve? Is this some kind of audit query?
Yes audit query is exactly what I am looking for. I saw the open-tx-log function, just seemed a bit inefficient to iterate over everything, but I think it will do for now.
Hi folks, I know I can check the source but would the following work? Would the current time be set as valid time?
[[:crux.tx/put {:foo :bar} nil] [:crux.tx/put {:quuz :baz} nil]]
well, I always check the source anyway 😅 I'm fairly certain that the answer is yes, because nil
will end up in the conformed tx-op map (which gets stored on the tx-log) even if you didn't have it as an extra element in the vector here, because of the destructuring and use of some->
in this method https://github.com/xtdb/xtdb/blob/e2f51ed99fc2716faa8ad254c0b18166c937b134/core/src/xtdb/tx/conform.clj#L46