This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-07-16
Channels
- # aleph (2)
- # announcements (1)
- # beginners (162)
- # calva (16)
- # cider (37)
- # cljdoc (9)
- # cljs-dev (2)
- # cljsrn (3)
- # clojure (86)
- # clojure-dev (17)
- # clojure-europe (3)
- # clojure-houston (1)
- # clojure-italy (6)
- # clojure-nl (3)
- # clojure-spec (10)
- # clojure-uk (20)
- # clojuredesign-podcast (15)
- # clojurescript (7)
- # data-science (14)
- # datascript (1)
- # datomic (5)
- # emacs (8)
- # figwheel-main (8)
- # fulcro (25)
- # graalvm (1)
- # jobs (10)
- # jobs-discuss (4)
- # keechma (14)
- # leiningen (2)
- # off-topic (31)
- # onyx (1)
- # other-languages (4)
- # pathom (4)
- # pedestal (1)
- # re-frame (20)
- # remote-jobs (4)
- # shadow-cljs (25)
- # sql (6)
- # tools-deps (15)
- # vim (18)
- # xtdb (9)
as in: Returns the transaction history of an entity, ordered by valid time / transaction time in chronological order, earliest first. Includes corrections, but does not include the actual documents.
Oh, I suppose "corrections" is a fairly general word for retroactive updates to an entity. We are working on a glossary which should help 🙂
is this to say, for a given document id, you would see all the shas that the document was at those points in time? Aka that would be a entry into getting the specific older versions via (document ...)
@U19EVCEBV yes I think that description is accurate. There's arguably room for a higher level API that combines the two stages of retrieval, especially for when going over HTTP
We just released 19.07-1.3.0-alpha
which has a breaking change due to eliminating use of the word "system" in favour of "node", so everyone will have to change things like start-standalone-system
to be start-standalone-node
(sorry!). Also included is crux-jdbc
, which is the beginnings of a fully featured JDBC backend (for use in place of Kafka, when Kafka isn't an option). Have fun!