Hi both, Thanks for taking the time to try to deal with my problem.
To add a bit of an extra detail to it, I'd want to write and query reasonably large (between 1-16 megabytes) values in an Oracle database but only one at a time. The values are stored in byte arrays or Strings, so I don't really need the stream semantics of standard LOB handling. Now querying isn't a problem, as ResultSet.getBytes() seems to work fine for any size values but Due to these limitations I thought about using OraclePreparedStatement.setBytesForBlob() to bind my values for write operations but there's no extension point I can find where I could do this. So as a limited (but still fairly generic) solution I thought about some kind of extension mechanism in the binding process, maybe an interface called 'SelfBindingValue', with a single method bindSelf( PreparedStatement ps, SQLDialect d) that is called by DefaultBindContext.bindValue0(). Or is there an obvious flaw in this idea? Thanks in advance, Peter On Wednesday, 27 March 2013 15:20:21 UTC, digulla wrote: > > 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.
