Hi Marcus, Yes indeed. Usually people already have a transaction manager like Spring or Java EE on their stack, so the jOOQ transaction API isn't really needed. Its main purpose is for use where JDBC transactions would also be useful, e.g. in batch jobs, lightweight stacks (only jOOQ and e.g. Spark Java), tests, etc.
Hope this helps, Lukas 2017-06-16 10:01 GMT+02:00 Marcus Gattinger <[email protected]>: > I see. Thank you very much for your help, Lukas, and sorry for my delayed > response. > > Although I haven't planned to use Spring for the transaction management, I > have tried it and as far as I can see it works very well with jOOQ. > > -- > 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. > -- 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.
