This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-03-20
Channels
- # announcements (1)
- # asami (2)
- # babashka (9)
- # babashka-sci-dev (33)
- # beginners (6)
- # calva (5)
- # cider (1)
- # clj-kondo (2)
- # clojure (79)
- # clojure-dev (8)
- # clojure-europe (1)
- # clojurescript (56)
- # core-logic (1)
- # datalevin (1)
- # emacs (20)
- # funcool (3)
- # holy-lambda (3)
- # honeysql (28)
- # improve-getting-started (11)
- # introduce-yourself (4)
- # lsp (21)
- # off-topic (9)
- # other-languages (5)
- # polylith (3)
- # quil (3)
- # releases (1)
- # rewrite-clj (9)
- # sql (5)
- # tools-deps (29)
- # xtdb (9)
Is there a way to get the transaction history for an entity, for cases where the valid time is overlapping (or even the same) (`entity-history` works when the valid times are distinct)?
There's a with-corrections?
option for this (if I understand correctly) - did you take a look at that already?
Ah, no. I didn't understand what corrections meant, so didn't see that as relevant. Thanks!
Hi @UCE6QCEQP that's correct, since Datalog always works in terms of sets of result tuples (even if there's only one result tuple). Were you expecting something different?
Hey @U899JBRPF! I understand reading the docs that the return values was a list.
Ah, so perhaps that definition is a bit too simplistic then - it could possibly say instead:
> The find clause of a query specifies the bound values to be returned in the query result tuples. Tuples are represented as lists. The query result is a deduplicated set of tuples, unless :limit
or :order-by
is specified, or open-q
is used, in which case the query result is a sequence of tuples.