Excellent. Thank you, Lukas. On Monday, October 5, 2015 at 12:29:20 PM UTC-4, Lukas Eder wrote: > > > > 2015-09-30 17:53 GMT+02:00 <[email protected] <javascript:>>: > >> I've read the following: >> . JOOQ documentation >> . https://groups.google.com/forum/#!topic/jooq-user/geYotcwEcRM >> . >> https://groups.google.com/forum/#!searchin/jooq-user/DSLContext$20thread-safe/jooq-user/ojz-EF9U4Cw/YwbDiJl7UxMJ >> . >> https://groups.google.com/forum/#!searchin/jooq-user/DSLContext$20thread-safe/jooq-user/VK7KQcjj3Co/lSI9anheMg0J >> >> After re-reading the above, my understanding is that DSLContext is >> thread-safe as long as the ConnectionProvider provides a connection that is >> not used by any other thread and that no application code in the thread >> using the DSLContext object modifies configuration state (dialect, >> settings, data). >> > > Exactly > > >> However, I'm wondering... Does JOOQ carry any transaction identifier or >> anything like that inside DSLContext that might make reuse of a DSLContext >> problematic within the context of an XA transaction? >> > > No - unless you implement that behaviour explicitly via ConnectionProvider > or TransactionProvider. > > Hope this helps, > Lukas >
-- 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.
