For tables that have non-null TEXT (blob) columns, mysqldbexport generates an insert statement with a null value for the column and then generates an update statement.
This wont work when mysqldbimport tries to load the file generates by mysqldbexport, as the import fails with a ERROR: Query failed. 1048 (23000): Column '<blob column>' cannot be null message.
Is there a way around this, or is this a known issue that needs to be fixed?
Or am I doing something wrong?
For tables that have non-null TEXT (blob) columns, mysqldbexport generates an insert statement with a null value for the column and then generates an update statement.
This wont work when mysqldbimport tries to load the file generates by mysqldbexport, as the import fails with a
ERROR: Query failed. 1048 (23000): Column '<blob column>' cannot be nullmessage.Is there a way around this, or is this a known issue that needs to be fixed? Or am I doing something wrong?