Bug #49007 "INNODB" not recognized properly

Submitted:	23 Nov 2009 23:27	Modified:	25 Nov 2009 15:33
Reporter:	Todd Farmer (OCA)	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench	Severity:	S2 (Serious)
Version:	5.2 r4753	OS:	Windows (XP)
Assigned to:		CPU Architecture:	Any

Description:
When setting the default storage engine, I noticed that WB indicated I had this already set in my.ini to MyISAM.  That's incorrect, and it appears that WB does not correctly parse the following:

default-storage-engine=INNODB

The server handles this just fine, creating table as InnoDB when no storage engine is explicitly defined.

Furthermore, changing the my.ini entry to use proper case allows WB to recognize it:

default-storage-engine=InnoDB

How to repeat:
Use default-storage-engine=INNODB in my.ini, see what WB says.

Suggested fix:
Use case-insensitive comparisons.

Fixed

fixed in repository. fix will be included in 5.2.9

An entry has been added to the 5.2.9 changelog:

MySQL Workbench did not parse the following entry in the my.ini file correctly:

default-storage-engine=INNODB

This resulted in the default storage engine not being detected correctly by MySQL Workbench, although this entry was correctly recognized by the MySQL server. However, MySQL Workbench did parse the following entry correctly, due to the correct capitalization being used:

default-storage-engine=InnoDB

Page generated in 0.052 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.