I'm not sure I entirely get it. How exactly does the connection / threadlocal mechanism in use case 2 operate? Would it try to get the ThreadLocal Configuration, and if it didn't exist, use / create a Configuration (with connection) from the using() arguments, and if it did exist, just ignore the using() arguments and use the ThreadLocal Configuration instead?
And does this mean if the query object passed into the fetch() (in your example "select().from(...)") is now thread safe and a single copy can be used in multiple threads? On Monday, September 9, 2013 5:58:24 AM UTC-4, Lukas Eder wrote: > > Hmm, I wonder though, if jOOQ should maintain a ThreadLocal somewhere, > referencing the Configuration for query / routine execution, instead of > attaching things... This would result in the following use-cases: > . . . > -- 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.
