Hi, I’m using next.jdbc and honey.sql to good effect in my app, everything going well. For much of my code, I use a single db execute! function that takes in vector of honeysql maps and returns the results. These statements are all run in a single jdbc transaction, allowing me to easily mock out the db for various tests and return arbitrary data from the ‘database’ in order to examine how the system works in various scenarios. I have built a mocking function that allows me to match a honeysql map, return whatever I want when a matched map is encountered, and examine the contents of that honeysql map to confirm that it is being populated as expected - happy days. I am testing the db directly as well of course in other tests but this model does away with the db population set up work, which can get tricky as the db gets more complex. So far, my db transactional requirements have been straightforward, and having a single transaction in this function has been sufficient for my needs. However, I am now encountering more scenarios where I need to handle more complex database-related logic, and I need to wrap more code with jdbc/with-transaction. My db mocking feature breaks down when I need to do this, - because jdbc/with-transaction is a macro and I can’t figure out a way to ‘mock’ this call (or do something that has the same effect) so I can concentrate on the correctness of my honeysql maps in my unit tests and not worry about a db. Any help on this would be appreciated, and happy to provide further information if helpful.