On Thu, 11 Mar 2010, Oliver Jowett wrote:
> You may have to run with a modified driver that you have patched to
> understand encodings other than UTF-8.
>
The JDBC driver does support running with a non-UTF-8 encoding, but only
for server versions prior to 7.3. There's no reason it couldn't work for
later versions, so the easiest thing to do is to tweak the v2 protocol
setup code to work for your server version and then use that.
Kris Jurka