Problem:
when myisam_conversion_innodb and tencent_myisam_conversion_innodb are
opened in instance, user execute following statement will fail.
CREATE TABLE trb9 (id INT, name VARCHAR(50), purchased DATE) ENGINE=MYISAM
PARTITION BY RANGE( YEAR(purchased) ) (
PARTITION p0 VALUES LESS THAN (1990) ENGINE=MYISAM,
PARTITION p1 VALUES LESS THAN (1995) ENGINE=MYISAM,
PARTITION p2 VALUES LESS THAN (2000) ENGINE=MYISAM,
PARTITION p3 VALUES LESS THAN (2005) ENGINE=MYISAM
);
the reason for this problem is that myisam_conversion_innodb only
convert the table engine to innodb but the partition engine still be
myisam so table engine and partition engine are different.
Solution:
Convert partition engine to innodb if it is myisam.
Problem:
when myisam_conversion_innodb and tencent_myisam_conversion_innodb are
opened in instance, user execute following statement will fail.
CREATE TABLE trb9 (id INT, name VARCHAR(50), purchased DATE) ENGINE=MYISAM
PARTITION BY RANGE( YEAR(purchased) ) (
PARTITION p0 VALUES LESS THAN (1990) ENGINE=MYISAM,
PARTITION p1 VALUES LESS THAN (1995) ENGINE=MYISAM,
PARTITION p2 VALUES LESS THAN (2000) ENGINE=MYISAM,
PARTITION p3 VALUES LESS THAN (2005) ENGINE=MYISAM
);
the reason for this problem is that myisam_conversion_innodb only
convert the table engine to innodb but the partition engine still be
myisam so table engine and partition engine are different.
Solution:
Convert partition engine to innodb if it is myisam.