This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-08-01
Channels
- # aleph (3)
- # announcements (10)
- # babashka (6)
- # bangalore-clj (4)
- # beginners (91)
- # biff (7)
- # cider (25)
- # cljs-dev (1)
- # clojure (109)
- # clojure-europe (9)
- # clojure-norway (5)
- # clojure-uk (1)
- # clojurescript (22)
- # cursive (22)
- # data-science (1)
- # datalevin (5)
- # datomic (7)
- # emacs (7)
- # etaoin (1)
- # events (3)
- # graphql (12)
- # hyperfiddle (1)
- # inf-clojure (1)
- # lsp (69)
- # luminus (1)
- # meander (21)
- # nbb (4)
- # off-topic (27)
- # other-languages (12)
- # rdf (58)
- # releases (3)
- # remote-jobs (2)
- # rum (12)
- # shadow-cljs (4)
- # sql (3)
- # xtdb (1)
I played around with cross db queries and it appears to work for Datalevin. But since the databases are not a value (immutable) it seems a little strange to have cross db queries. Is this feature going to stay? General thoughts around this?
It stays. Why would it be strange? In my mind, DB is just a surrogate of some external world state, and there can be multiples of them
As mentioned in my talk two years ago, I don't buy the DB as value story. DB is the state, just like most people believing it to be. If DB is value, you don't need ACID
With MVCC I am guessing these reads can still happen in the read transaction without blocking the writes. So you would just want to open a read transaction at the same time for each db.