This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-04-01
Channels
- # announcements (54)
- # asami (3)
- # aws (5)
- # babashka (8)
- # beginners (64)
- # biff (27)
- # calva (11)
- # cider (41)
- # clj-otel (7)
- # cljdoc (72)
- # clojars (20)
- # clojure (159)
- # clojure-austin (3)
- # clojure-europe (143)
- # clojure-italy (1)
- # clojure-nl (5)
- # clojure-norway (3)
- # clojure-uk (3)
- # clojurescript (19)
- # community-development (1)
- # core-typed (5)
- # cursive (3)
- # datalevin (1)
- # datomic (8)
- # emacs (13)
- # fulcro (4)
- # google-cloud (4)
- # honeysql (25)
- # java (1)
- # jobs (1)
- # lambdaisland (3)
- # lsp (121)
- # off-topic (52)
- # other-languages (1)
- # re-frame (3)
- # releases (2)
- # remote-jobs (1)
- # shadow-cljs (36)
- # sql (4)
- # xtdb (36)
I found https://clojurians-log.clojureverse.org/sql/2020-06-04 about nested transactions in next.jdbc. My use case is the same, I don't want nested transactions in prod, but I wanted to use an outer transaction in tests to rollback changes during a test. The code under test opens a transaction. Is there any movement on this since then? Or had anyone come up with an alternative solution for running tests against the database that don't dirty the database afterwards?
@ramblurr See https://cljdoc.org/d/com.github.seancorfield/next.jdbc/1.2.772/api/next.jdbc.transaction#*nested-tx*
❤️ 1