Don't worry, I do know how to do it, it's just that in the existing
BioJava-live code it hasn't been done, and I'll need to be careful to
add the usual checks to see if we're using Oracle or not before choosing
the appropriate SQL to update biosequence with.
CLOBs under 4000 chars are certainly ea
Mark Schreiber wrote:
> store sequence. The biojava support code seems to assume LONGs and
> strangely until very recently the JDBC oracle dirver seems to let you
> write LONGs to CLOBs although the data that comes out again is completely
> munged.
>
> It would be possible to modify the biojav
CLOB is IMHO actually easier to handle. Also, LONG is really odd to
deal with in SQL whereas the Oracle server will nicely on-the-fly
convert strings to CLOB and vice versa so long as they are shorter than
4000 chars. Some of the type-generic functions that come with Oracle
will not accept LONG
I looked into this in a bit more detail earlier today and found that,
since some version of Oracle around the 9i point in time, the official
Oracle JDBC driver API for accessing LOBs in changed. This means that
whereas before the same code could be used in BioJava to access both
Hilmar's and Len's
We tracked down the error to the fact that the Hilmar Oracle version (no
assertion is made about the complexity) uses CLOBs to store sequence while
the Len Oracle (no assertion about simplicity etc) version uses LONGs to
store sequence. The biojava support code seems to assume LONGs and
strange
