Details
Major
Description
When backing up a database with MYSQL_TYPE_GEOMETRY fields, mysqldump will output those fields in binary format by default. This causes issues upon restore.
The typical error returned by mysql when restoring such a dump is :
"Cannot get GEOMETRY object from the data you send to the Geometry field".
Using the --hex-blob option fails to treat GEOMETRY types as blobs.
A simple solution is to change the following line in mysqldump.c
field->type == MYSQL_TYPE_TINY_BLOB)) ? 1 : 0;
for
field->type == MYSQL_TYPE_TINY_BLOB ||
field->type == MYSQL_TYPE_GEOMETRY)) ? 1 : 0;
Gliffy Diagrams
Attachments
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
Hi Elena,
I'm having a hard time locating an exact instance of a data dump with failing details.
I will try to generate one from some past records we've had issues with.
Regardless of that, the problem with dumping data as binary in an SQL file is also one of charsets and carriage return interpretation.
This is of particular importance or interest when working accross platforms and trying to extract or manipulate SQL statements from a dump accross MariaDB installations of deployments.
mysqldump should have the ability to dump all records in non-binary format regardless of type in order to avoid corruption of data when moving charsets around.
Geometry objects being the only other record type to store binary information appart from Blobs, I propose it should either be considered as a Blob as well or alternatively have a switch like "--hex-geometry" to allow for non-binary dumping.
Best regards,
Guillaume
pushed into 5.3
Hi,
Could you please provide an example of the data which triggers the error? It would be useful for testing.
I tried some primitive values and didn't get into any trouble, so apparently it does not happen always.