This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-11-09
Channels
- # announcements (14)
- # architecture (42)
- # babashka (23)
- # beginners (37)
- # biff (8)
- # calva (2)
- # cider (3)
- # clara (42)
- # clerk (14)
- # clojure (55)
- # clojure-brasil (3)
- # clojure-dev (5)
- # clojure-europe (18)
- # clojure-hungary (88)
- # clojure-losangeles (3)
- # clojure-nl (1)
- # clojure-norway (66)
- # clojure-uk (9)
- # clojurescript (16)
- # core-logic (16)
- # datomic (6)
- # fulcro (32)
- # hyperfiddle (25)
- # instaparse (12)
- # joyride (2)
- # lsp (13)
- # malli (15)
- # off-topic (50)
- # polylith (11)
- # portal (3)
- # re-frame (2)
- # reitit (2)
- # sci (8)
- # shadow-cljs (16)
- # tools-deps (13)
- # xtdb (5)
does :db/op :create support a map argument like :db.op/upsert for determining the document's identity?
No, though I suppose that might be worth adding. You can instead use the :biff/ensure-unique transaction function directly. I'll post an example when I'm at my desk
The combination of :http://db.id/my-id and fixtures.edn is very nice!
That's why I added support for : 🙂
lol, nice
Perhaps recklessly, I'm deploying to rocksdb. I'm wanting a function I can use to make a backup copy of the tx-log and, if needed, the document store, while the production system is running. and also a way to restore a system from such a backup.
you should be able to write some backup/restore functions using XT's transaction log API. I haven't written these myself yet, but I would like to at some point... probably have them store the backups in S3/DO spaces
I actually run Yakread on just rocksdb and for that I'm just relying on DO's weekly filesystem backups. worst case scenario I could lose a few days of data... but it's not like I'm making a bunch of money from Yakread anyway 🤷