|
|
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Kevin A. Burton wrote:
> Mark Matthews wrote:
>
>
>>Kevin,
>>
>>You'll have to go back and make sure you understand the charset stuff in
>>4.1 _very_ well...It's not as simple as it was in 4.0 (of course it's
>>more powerful).
>>
>>
>
> I've just breezed through it a bit.. I was hoping that I could leave
> everything the same as latin1 and that the JDBC driver would do the
> encoding for me which doesn't seem too insane...
>
>
>>The issue you're having is that you're telling the JDBC driver to send
>>everything to the database in UTF-8, which is fine, but from the output
>>you just set from 'show variables', your database is using all 'latin1'
>>characters and collations (the default collation for the latin1
>>character set is 'latin1_swedish_ci').
>>
>>If you leave your database in that 'state', along with the tables, and
>>don't do cast and/or convert functions in your queries, you will always
>>get this error, as you the SQL standards doesn't allow silent
>>conversions or comparisons utf-8 character sets with anything else other
>>than utf-8 character sets.
>>
>>
>>
>
> What I want to do is just make the DB blind as it was in MySQL 4.0... I
> don't have the time to spend converting our data.
>
>
>>Just using 'useUnicode=...&characterEncoding=...' worked with MySQL-4.0,
>>because it had no idea what utf-8 was, so it just treated everything as
>>a set of byte[]s.
>>
>>
>
> Yes... and I wanted to maintain that behavior as I don't want to spend 2
> weeks converting all our data.
>
>
>>MySQL-4.1.8 will have utf-8 versions of collations for all other
>>character sets (as far as I know),
>>
>
> OK... so I just use a collation of latin-utf8 which will except utf8
> data and save it in a latin1 table? I guess this would provide the
> default behavior as before.
>
>
>>so you might want to wait and see if
>>this will fix the problem in your case without you having to alter any
>>of your tables. Probably worth checking out of bk and testing now, afaik
>>the code is already in there.
>>
>>
>
> Sounds like what we want. Whats the ETA to 4.1.8?
>
>
>>(and yes, we know the new character set support can be painful for
>>upgrades for those people using utf-8, so hopefully 4.1.8 and newer will
>>solve that).
>>
>>
>
> It seems like this should be documented. I'm willing to bet there are a
> LOT of JDBC users out there who were doing the UTF8 encoding in their
> driver and want the same behavior in 4.1.x...
Kevin,
It is documented in the 'upgrading from 4.0 to 4.1' section in the
server manual, however you've already gone on record that you don't like
what the upgrade process would entail, so....
>
> I can think of 1/2 dozen big shops that are doing that right now...
>
> Kevin
>
If you're willing to be a guniea pig, ping me, and I'll send you a copy
of the JDBC driver that has a switch to make it act like it does when
it's talking to MySQL-4.0...
-Mark
- --
Mark Matthews
MySQL AB, Software Development Manager - Client Connectivity
Office: +1 708 332 0507
www.mysql.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFBtieotvXNTca6JD8RAhG7AJ9aWji789Jwp6pX3grMKmfX9piINQCfX9Pm
Zv82HLYkxf1vVs6Q8XzX70k=
=XRvN
-----END PGP SIGNATURE-----
--
MySQL Java Mailing List
For list archives: http://lists.mysql.com/java
To unsubscribe: http://lists.mysql.com/java?unsub=mailarch@xxxxxxx
|
|