Hi Lukas, Thanks for your replies. I just want to say that your openness to talking about consider improvements to your API is very refreshing, and an all too rare thing in the software world.
I would swear that when I stepped over my bind() call in the debugger I saw a different object returned than the query on which I executed it. I must have misinterpreted something. I'm happy to hear that some of these issues may be addressed in a JOOQ 4, and that there is a way to detach queries. Let me just make sure I'm interpreting your replies correctly around query objects and thread safety. It looks like my options are: 1) don't hold onto a query object, rebuild the query object each time I execute it 2) build it once, extract the sql and hold onto that instead of the query object, and when I want to execute it, instantiate new query object, using DSLContext.resultQuery (in my "select" cases, at least) 3) hold onto the query object and synchronize the lines where I attach, bind, and execute (probably not really desirable but just listing it for completeness) Is that right or are there other options I missed? Thanks again, Eric -- 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.
