This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-05-18
Channels
- # announcements (2)
- # asami (20)
- # aws (4)
- # babashka (35)
- # beginners (47)
- # calva (65)
- # cider (19)
- # clj-kondo (63)
- # clojure (177)
- # clojure-austin (2)
- # clojure-europe (27)
- # clojure-nl (1)
- # clojure-uk (4)
- # clojurescript (13)
- # community-development (5)
- # conjure (5)
- # css (2)
- # data-oriented-programming (9)
- # datalevin (13)
- # datascript (15)
- # datomic (4)
- # devcards (6)
- # duct (4)
- # emacs (8)
- # funcool (1)
- # gratitude (2)
- # helix (3)
- # hyperfiddle (3)
- # introduce-yourself (1)
- # jobs (4)
- # jobs-discuss (26)
- # lambdaisland (2)
- # lsp (20)
- # malli (2)
- # meander (2)
- # mid-cities-meetup (5)
- # missionary (15)
- # music (4)
- # off-topic (37)
- # reagent (3)
- # reitit (2)
- # releases (2)
- # ring (18)
- # shadow-cljs (70)
- # specter (4)
- # sql (20)
- # timbre (3)
- # tools-build (43)
- # tools-deps (11)
- # vim (29)
- # xtdb (61)
Hello. Using server/client mode. Weird issue if anyone has an idea shots going on. If I keep my connection open, any add transaction using transact! deletes the previous transaction. It's fine if I close connection in between. Not sure if related or not but repl on client always comes back with `{:datoms-transacted 0} Using 0.6.11 on windows Thanks!`
Basically the new transaction writes to the same db/id without incrementing it. Each transaction is a vec of maps with each map having :db/add -1
Update: it works if I manage and increment db/id myself - obviously not ideal
Fair I'll do later as no access to slack from work and painful on phone. But my transactions work fine with a local db, it's in client/server mode that the max-eid doesn't update automatically for some reason.
Awesome thx!
You're a star! Thanks!