Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: CMT8.4.1.201211
-
Fix Version/s: CMT8.4.1.201211
-
Component/s: CUBRID Migration Toolkit
-
Labels:
-
Environment:
CMT8.4.1.3079
From mysql to sql
Description
1There is one table in mysql:
CREATE TABLE `1int` (
`i` int(11) DEFAULT NULL,
`iu` int(10) unsigned DEFAULT NULL,
`mediumint1` mediumint(9) DEFAULT NULL,
`tinyint1` tinyint(4) DEFAULT NULL,
`tinyint unsigned1` tinyint(3) unsigned DEFAULT NULL,
`mediumintunsigned1` mediumint(8) unsigned DEFAULT NULL,
`smallint1` smallint(6) DEFAULT NULL,
`smallintunsigned` smallint(5) unsigned DEFAULT NULL,
`tinyintn1` tinyint(1) DEFAULT NULL,
`a` smallint(6) DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1
2 Do migration from mysql to sql.
Choose the table ,click next, it will pop error for "tinyint unsigned1", change it to "tinyintunsigned1"
3 Do migration.
Actual result:
The sql is "tinyint unsigned1" too.
The sql is :
INSERT INTO "1int"("i","iu","mediumint1","tinyint1","tinyint unsigned1","mediumintunsigned1","smallint1","smallintunsigned","tinyintn1","a")VALUES(-2147483648,4294967295,8388607,127,255,16777214,32767,0,-123,NULL);
fixed