Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: CMT8.4.1
-
Fix Version/s: CMT8.4.1
-
Component/s: CUBRID Migration Toolkit
-
Labels:None
-
Environment:
CMT2.0.0.4873
Description
1 Create table in mysql
CREATE TABLE `binarytest` (
`binary1` binary(1) DEFAULT NULL,
`binary255` binary(255) DEFAULT NULL,
`binary30` binary(30) DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
INSERT INTO `binarytest` VALUES ('2', '2323333fdsafasdfdsafsdfsdaf', 'fasdfasdfsdafsafds');
INSERT INTO `binarytest` VALUES ('a', 'estchangdTestchangdTestchangdTestchangdTestchangdTestchangdTestchangdTestchangdTestchangdTestchangdTestchangdTestchangdTestchangdTestchangdTestchangdTestchangdTestchangdTestchangdTestchangdTestchangdTestchangdTestchangdTestchangd高stchangdTestchangdTestch', 'TestchangdTestchangdTestchangd');
2 Do migration
Actual result
After migration, the data of binary(255) cannot be migrated.
The data was not lost in the migration,It just was turned to BIT data type.
We add a feather that binary(MYSQL) can be transformed into char(CUBRID)