>+1. Nice catch.
Well... Almost, but not quite.
the mm.mysql JDBC drivers don't SUPPORT setCharacterStream(). They
do, however, support the deprecated setUnicodeStream() which is the
same as setAsciiStream, except it expects the stream in UTF-8 data
format and sends unicode to the database instead of ascii... So...
That's what I'm using now. I'm doing a getBytes("UTF8") instead of a
getBytes(), and setUnicodeStream() instead of setCharacterStream().
Could everyone perhaps test out their JDBC drivers to see which ones
support setCharacterStream()? If mm.mysql is the ONLY one that
doesn't support it, it should be pretty trivial to fix it so that it
does. I mean, there's no real reason why setCharacterStream
shouldn't work when setUnicodeStream does.
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]