Re: ENCODE() on MySQL 5.0 differs from 5.5+
Posted by: Rick James
Date: November 14, 2012 08:02PM

But what client were you using? "cmd" with "mysql"? Something else?

cmd has an encoding built in; I don't know how to ask what it is. Perhaps that has changed between the two versions of Windows, or somehow the setting was changed at some point.

The fact that the HEX is the same is good -- it means that the ENCODE function has not changed.

What is the datatype of the field with the encrypted value? It really should be VARBINARY or BLOB. In that case, you can use --hex-blob on the mysqldump to avoid any charset issues during dump and reload.

Options: ReplyQuote

Written By
Re: ENCODE() on MySQL 5.0 differs from 5.5+
November 14, 2012 08:02PM

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.