MySQL Forums
Forum List  »  General

Re: Strange behavior between mysql versions with binary
Posted by: Laurent MINOST
Date: May 02, 2012 08:03AM

Hi Rick,

Thanks for your answer,

I did the test from my command line mysql client on each servers :

From dedwen :

mysql> SELECT name, HEX(name), LENGTH(name), CHAR_LENGTH(name) FROM redonline_foodsafety.theme WHERE name like binary 'Précaution';
+------------+------------------------+--------------+-------------------+
| name | HEX(name) | LENGTH(name) | CHAR_LENGTH(name) |
+------------+------------------------+--------------+-------------------+
| Pr�caution | 5072C3A963617574696F6E | 11 | 10 |
+------------+------------------------+--------------+-------------------+
1 row in set (0.02 sec)


From djen :

mysql> SELECT name, HEX(name), LENGTH(name), CHAR_LENGTH(name) FROM redonline_foodsafety.theme WHERE name like binary 'Précaution';
+------------+------------------------+--------------+-------------------+
| name | HEX(name) | LENGTH(name) | CHAR_LENGTH(name) |
+------------+------------------------+--------------+-------------------+
| Pr�caution | 5072C3A963617574696F6E | 11 | 10 |
+------------+------------------------+--------------+-------------------+
1 row in set (0.03 sec)

Results seems to be the same for both servers.

I was not able yet to do the tests from Toad.

Do you think the problem comes from the bad charset / collation set for the client ? but why is it working from Toad for one server and not for the other if data are the same and charset/collation are equal ?

Thanks,
Regards.

Laurent

Options: ReplyQuote




Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.