On Wed, 23 Mar 2005, Michael Barker wrote:
> I will have a look at the patch over the weekend. When I wrote the CLOB
> stuff I set it up to always use a single byte encoding, except when using
> get/setCharacterStream. If a user required mulltibyte encodings then they
> should use the Reader/Writer combination exclusively.
AbstractJdbc2Clob.getSubString creates a String from bytes with no
encoding specified.
AbstractJdbc3Clob.setString(long, String, int, int) gets a String's bytes
with no encoding specified.
Even when the user wants a multibyte encoding they are stuck using the
JVM's default encoding because the Reader/Writer's are not created with an
encoding specified.
Yeah, it's a complicated issue. I know you were after just the BLOB part
and I pushed you into the CLOB part. No one else has any feedback, and no
matter what we do it won't be all that good, so maybe the smart thing to
do is just to abandon the CLOB part and just put the BLOB in by itself.
Not to discourage you if you really are interested in the CLOB part of it,
just letting you know that it's not a prerequisite for the BLOB part to
get in.
Kris Jurka
