Comments
3 comments
-
After continuing to troubleshoot the problem, I have validated that it's NOT related to the BINARY(16) id, but rather to a TEXT field we have.
If I remove the two TEXT fields from the compare the compare work, however I do not understand why MySQL Data Compare see the TEXT field as a BLOB (as mentionned in the error message). -
Thank you for your forum post.
For this table, are the schemas identical? You can check this using MySQL Compare.
I suspect that the column in the source database is using a BLOB data type and the target is using the TEXT data type. The Devart components used by MySQL Data Compare cannot cast data from a MySQLBlob to MySQLText and hence the deployment fails.
Many Thanks
Eddie -
I used MySQL Compare to make sure, but both table were identical (TEXT), we managed to make it work, but we had to convert both TEXT field to VARCHAR(65,534) and it worked.
Add comment
Please sign in to leave a comment.
I'm having issue when I'm trying to synchronize my data from my preview environment to my testing environment.
Our primary key are BINARY(16) and are UUID. We have some other fields but I'm not sure that's relevant. When I'm trying to synchronize the data (import the data from an environment to another), I'm getting this error :
Bug report generated at 2014-05-28 11:59:31
Program version 1.0.0.473
Is there anything I'm doing wrong ? I could always drop the table and do a backup restore of the data I want to keep, but it worry me that it's not working.
Regards,
Jonathan