wow, thanks!

will try it again, thanks

I think the rollback issue may be caused by HikariCP

it is not rolled back even with exception

are nested transactions noops?

yes! it works if nested transactions removed

another question, is there a select … for update helper?

Just want to say one more time huge thank you for your work on jdbc.next

@kirill.salykin Take a look at HoneySQL for helpers for building SQL. Not sure if select-for-update is supported there (but it's easy to extend to support new syntax). next.jdbc itself is never going to support more SQL than it does today (I nearly didn't add the next.jdbc.sql namespace at all -- but figured folks using clojure.java.jdbc would expect those functions).

i just used execute-one for now

As for nested transactions, JDBC doesn't really support that: transactions are per-connection and you can rollback/commit/savepoint as needed.

I updated the Transactions page to make a lot of that clearer https://github.com/seancorfield/next-jdbc/blob/master/doc/transactions.md

seems like nested transatcion were not rollback’able

clojure.java.jdbc "allowed" you to nest transactions but it simply ignored nested transactions and everything happened in the top-level transaction.

> seems like nested transatcion were not rollback’able That page explains why (and why you shouldn't do that 🙂 ).

clear, thanks!