This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-01-16
Channels
- # announcements (2)
- # babashka (51)
- # beginners (165)
- # biff (39)
- # clara (1)
- # clj-kondo (20)
- # cljsrn (6)
- # clojure (64)
- # clojure-belgium (11)
- # clojure-conj (2)
- # clojure-europe (12)
- # clojure-nl (3)
- # clojure-norway (7)
- # clojure-uk (6)
- # clojurescript (11)
- # conf-proposals (1)
- # conjure (1)
- # core-async (19)
- # cursive (6)
- # data-science (16)
- # datomic (6)
- # deps-new (4)
- # fulcro (60)
- # funcool (3)
- # graalvm (9)
- # helix (14)
- # introduce-yourself (4)
- # jobs-discuss (13)
- # joyride (1)
- # kaocha (2)
- # malli (12)
- # off-topic (25)
- # polylith (9)
- # portal (3)
- # practicalli (1)
- # rdf (43)
- # re-frame (7)
- # reagent (5)
- # releases (5)
- # remote-jobs (8)
- # sci (5)
- # shadow-cljs (42)
- # squint (6)
- # xtdb (5)
hello, i'm considering using xtdb for the app i'm working on. It's a software that's running on the client's PC and therefore improper shutdown could happen. Is xtdb's embedded mode reliable or is that mode mostly for testing ? has anyone experienced data corruption with the embedded version ?
I would think it’s more about what you are using as your golden stores (tx-log and doc store) that matters
most storages proposed look robust. I guess there still the potential inconsistency between log and doc store. But if the document is written before the event the issue is probably non existent ? just a document version that will never be referenced
hey fyi,https://xtdb.com/docs/ appear to break routing after going to them. Try clicking "Datalog Transactions" then on the following page click "Learn" (or any other nav link). It looks like it has something to do with the docs subdomain messing up relative refs
Hey @U036QHV2M4Z thanks for mentioning this. We're investigating and will hopefully have it fixed tomorrow. Sorry for the confusion 😅