MySQL Bugs: #79070: Workbench 6.3.5 not handling partitions when showing Alter Table page

Bug #79070	Workbench 6.3.5 not handling partitions when showing Alter Table page
Submitted:	2 Nov 2015 12:05	Modified:	9 Dec 2015 5:25
Reporter:	IGG t	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench	Severity:	S3 (Non-critical)
Version:	6.3.5	OS:	Windows (7)
Assigned to:		CPU Architecture:	Any
Tags:	alter, regression, workbench

Description:
When doing right click > Alter Table on a table in the SQL editor, if that table contains partitions the results are strange.

With a MySQL 5.5.45 Database it gives an error "Error Parsing DDL for TableName"

With a MySQL 5.7.9 Database it opens the editor window, but the partitions are not shown.

How to repeat:
create a table:
CREATE TABLE test.testTable (
  `id` int(10) unsigned NOT NULL AUTO_INCREMENT,
  `TIME` datetime NOT NULL,
  `SERVER` varchar(45) NOT NULL,
  `TCO` mediumint(8) unsigned DEFAULT NULL,
  PRIMARY KEY (`id`,`TIME`),
  KEY `ixSERVER` (`SERVER`)
) ENGINE=InnoDB AUTO_INCREMENT=1 DEFAULT CHARSET=latin1
/*!50100 PARTITION BY RANGE ( TO_DAYS(TIME))
( PARTITION `201510` VALUES LESS THAN (736268) ENGINE = InnoDB,
 PARTITION `201511` VALUES LESS THAN MAXVALUE ENGINE = InnoDB) */;

Locate the table in the schemas list, right click and select 'Alter Table'

In MySQL 5.5 you should get the above error.

In MySQL 5.7 it should open ok. Navigate to the 'Partitioning' tab, and you should see no partitions listed.

Suggested fix:
Workbench should open the Alter Table window ok, and display the partitions.

Hello!

Thank you for the report.

Thanks,
Umesh

6.3.4 Screenshot..

Attachment: 79070_6.3.4.png (image/png, text), 60.44 KiB.

6.3.5 Screenshot..

Attachment: 79070_6.3.5.png (image/png, text), 53.48 KiB.

Posted by developer:
 
Fixed as of the upcoming MySQL Workbench 6.3.6 release, and here's the changelog entry:

The Alter Table tool did not function with partitioned tables.

Thank you for the bug report.

I am using Workbench 6.3.8 build 1228 CE (64bits) and I still get the same error msg on a partitioned table.

still happens 
Workbench version 6.3.10
Mysql Server 5.5

I am getting this error on version 6.3.9