Hi, things are going mostly amazing with jOOQ. Even though it may be 6 years old it is a breath of fresh air in the face of complex Spring and JPA based applications.
So I'm creating my own Transaction abstraction on top of jOOQ that reference counts transactions in the same thread instead of creating save points. So it shares transactions when they nest (by default). There are other #transactionResult like methods that for example, force a new transaction or a save point, but I doubt I'll ever use these last two, they are just there for completeness. I notice that in your version of #transactionResult that you ALWAYS derive the existing Configuration instance. Before I get rid of this in my abstraction I wanted to know if there was a specific reason for the new object creation? It *seems* like the derived configuration just shares maps and stuff from the old configuration so I'm not sure what the reason for this is. Thanks! -- You received this message because you are subscribed to the Google Groups "jOOQ User Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
