Closed tomekw closed 2 years ago
That is specifically called out as a caveat in the documentation: https://cljdoc.org/d/com.github.seancorfield/next.jdbc/1.2.780/doc/getting-started#datasources-connections--transactions
Since next.jdbc
using raw Java objects for Connection
etc, you have to explicitly re-wrap them yourself if you want options to carry across with-transaction
.
A while back, I spent a fair bit of time looking into the possibility of having with-transaction
automatically rewrap the options if it was asked to create a Connection
with a transaction from a wrapped datasource or connection and concluded it wasn't realistic to do it automatically: https://github.com/seancorfield/next-jdbc/issues/172
Oh, my bad!
Especially when I tweeted this today in the morning:
https://twitter.com/_tomekw/status/1522490350878797824
🤦
Thank you!
Describe the bug
with-transaction
doesn't respect:builder-fn next.jdbc.result-set/as-kebab-maps
I've
db
defined as:To Reproduce
Expected behavior
project.clj/deps.edn
Environment (please complete the following information):