Re: ENCODE() on MySQL 5.0 differs from 5.5+

[Carl Dreher]

Well, this IS interesting.

On the XP-Pro, 32-bit system, MySQL 5.0, the command
ENCODE('password','abcdedghijklmnopqrstuvwxyz') returns
ºƒŽ%aôÝ

but on the W7-64bit system with MySQL 5.5, it returns
º??%aôÝ

But if I wrap each command in the HEX operator, as per your suggestion, they both return the same value
BA838E2561F41ADD

Both systems are using the Latin1 char set.

The problem this caused was when I did a SQL "dump" of the database from the XP system, which generates a large file full of SQL statements, including statements such as
INSERT INTO passwords VALUES(ºƒŽ%aôÝ)
Then I then ran this file in the W7 system to create and build the database. Naturally, when I tried to use it, all the passwords didn't DECODE correctly.

Still wondering what is going on.