Note, I meant to say that DSLContext is not explicitly thread-safe. You
*can* however achieve a thread-safe environment by carefully implementing
ConnectionProvider and possibly other SPI types that are used by
org.jooq.Configuration


2013/11/5 Lukas Eder <[email protected]>

> Hi Aym,
>
> No it is not thread-safe, much like the underlying Connection is hardly
> threadsafe in most transaction / data source contexts (what are you using
> to make Connection thread-safe?)
>
> Here are a couple of interesting reads on the jOOQ user group about
> DSLContext / Configuration thread-unsafety:
>
> - https://groups.google.com/d/msg/jooq-user/Y_tfF_eaxKM/jINIU3RYmiYJ
> - https://groups.google.com/d/msg/jooq-user/iomrnfK9cws/QFVH7Ts2iEcJ
> - 
> https://groups.google.com/d/msg/jooq-user/OW58UXvljhU/NDTqFasaJv0J<https://groups.google.com/forum/#!msg/jooq-user/OW58UXvljhU/NDTqFasaJv0J>
>
> Cheers
> Lukas
>
>
> 2013/11/5 <[email protected]>
>
> Hello,
>>
>> Sorry if this is obvious, but is DSLContext created from
>> DSL.using(DataSource) threadsafe (given datasource and underlying
>> connection is threadsafe) ?
>>
>> Cheers
>> Aym
>>
>> --
>> 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/groups/opt_out.
>>
>
>

-- 
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/groups/opt_out.

Reply via email to