Bug #42763 | Indexe won't be migrated | ||
---|---|---|---|
Submitted: | 11 Feb 2009 13:58 | Modified: | 6 Feb 2013 23:07 |
Reporter: | Susanne Ebrecht | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL Workbench | Severity: | S2 (Serious) |
Version: | 1.1.17 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[11 Feb 2009 13:58]
Susanne Ebrecht
[2 Apr 2009 7:43]
Valeriy Kravchuk
Latest MT migrates table defined as: SQL> create table t(i number, n number); Table created. SQL> alter table t add primary key(i); Table altered. SQL> create index i_n on t(n); Index created. in Oracle into MySQL equivalent: DROP TABLE IF EXISTS `system`.`t`; CREATE TABLE `system`.`t` ( `i` DECIMAL(22, 0) NOT NULL, `n` DECIMAL(22, 0) NULL, PRIMARY KEY (`i`), INDEX `i_n` (`n`) ) ENGINE = INNODB; So, the bug is PostgreSQL-related.
[2 Apr 2009 9:59]
Susanne Ebrecht
Many thanks Valeriy. Your test means that this is only common JDBC related. Set back to verified.
[6 Feb 2013 23:07]
Alfredo Kojima
No longer applies in WB