On 7 April 2013 17:18, Christopher Deckers <[email protected]> wrote: > > Witold, Lukas, > >> > Where >> > to get the "create" from? It doesn't matter. > > > Oh yes it does. If the same object instance is supplied to several calls, > this could result in awful issues in case of multi-threading or usage of > fetchLazy. > The only safe way to execute an SQL call in an application without worrying > of concurrent uses is to call "using()". Only the Configuration is guaranteed > (if not by implementation, by contract) to be a safe object to use across an > application.
I promised not to mention about this anymore, but I have to deny what was said above. Christopher, this is not true what you say about "the only safe way...". The solution you mention, this is the "using(configuration)" is flawed. I am not going to continue about this anymore, as everything was said. There are at least few (maybe a dozen) ways to guarantee, across entire application, that Executor will be used safely without spreading the configuration across entire application, forcing users to call some factory to exchange config for Executor. In my most recent application, using EJB/CDI container, everything works correctly "out of the box". Previous one used plain Tomcat without any extra containers, and yet it was also enough to keep the details of creating Executor (called FactoryOperations in 2.6) away from it's customers. Regards, Witold Szczerba -- 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.
