Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: CMT8.4.1.201209
-
Fix Version/s: CMT8.4.1.201209
-
Component/s: CUBRID Migration Toolkit
-
Labels:
-
Environment:
CMT8.4.1.3022
From mysql to CUBRID8.4.1.6004
Description
1 There are two tables.
CREATE TABLE `A` (
`i` int(11) DEFAULT NULL,
`d` int(11) DEFAULT NULL,
`a` int(11) DEFAULT '0',
KEY `A_ab` (`i`),
CONSTRAINT `A_ab` FOREIGN KEY (`i`) REFERENCES `ab` (`a`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1
CREATE TABLE `a` (
`a` int(11) NOT NULL DEFAULT '0',
`b` int(11) DEFAULT NULL,
`c` int(11) DEFAULT NULL,
`d` int(11) DEFAULT '0',
PRIMARY KEY (`a`),
KEY `a_b_id` (`b`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8
CREATE TABLE `ab` (
`b` decimal(63,0) DEFAULT NULL,
`a` int(11) NOT NULL DEFAULT '0',
PRIMARY KEY (`a`),
KEY `b_idx` (`b`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1 COMMENT='aaaass'
2 Do migration from online to online.
3 Goto step3, only choose A and a
4 Click next, it will pop the error as attachement.
If click the fk in A, needn't change anything, it can be ok.
by design. Users must know this error.