We found, to our chagrin, that a dump of an encoded field does not
restore properly in all cases.
Specifically, we use encode() to code credit card numbers before inserting
them in the database. We did a mysqldump to produce a transport file
from version 3 of mysql to insert the data into
We did a mysqldump to produce a transport file
from version 3 of mysql to insert the data into version 4 of mysql.
The encoded numbers were munged, presumably because they were
binary data in the dump.
Isn't this what the --hex-blob option to mysqldump is for?
--
MySQL General Mailing List
We did a mysqldump to produce a transport file
from version 3 of mysql to insert the data into version 4 of mysql.
The encoded numbers were munged, presumably because they were
binary data in the dump.
Isn't this what the --hex-blob option to mysqldump is for?
There is no such option to
Isn't this what the --hex-blob option to mysqldump is for?
There is no such option to mysqldump in version 4.1.11.
From the manual:
--hex-blob
Dump binary string columns using hexadecimal notation (for example,
'abc' becomes 0x616263). The affected columns are BINARY, VARBINARY,
and BLOB
