Hi Aaron, Yes, I had noticed that question. Thanks a lot for answering it. Indeed JDBC's Blob/Clob handling doesn't really fit well into jOOQ's type management philosophy. It is far from trivial to get this right, as InputStream / OutputStream lifecycles may not match that of a query execution. In other words, fetching a LOB without immediately consuming it might compromise jOOQ's model of when to "release()" a used connection - to use the term from recent discussions.
Nonetheless, the current situation is not satisfying, as ignoring LOB existence isn't a good long-term strategy for jOOQ :-) I'm very open to suggestions and implementation ideas. When I have time, I'll also comment on that question. Cheers Lukas 2013/3/27 digulla <[email protected]>: > Hi Lukas, > > The question came up on SO: > http://stackoverflow.com/questions/15642421/b-clob-handling-in-jooq > > I posted some code, maybe you can have a look at it. > > Regards, > > A. Digulla > > -- > 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.
