Bug #49011 WB needs to be version-aware when adding new configuration options
Submitted: 24 Nov 2009 0:03 Modified: 19 Apr 2010 14:37
Reporter: Todd Farmer (OCA) Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench: Administration Severity:S1 (Critical)
Version:5.2 r4753 OS:Windows (XP)
Assigned to: Maksym Yehorov CPU Architecture:Any

[24 Nov 2009 0:03] Todd Farmer
Description:
I used WB 5.2 to configure my MySQL 5.0.67 server running locally on Windows XP.  I have the following defined in my.ini:

log=general.txt

In 5.0, this both enabled the general query log and sets the name of the output file.  However, WB appears to key off of the new 5.1 "general-log" option, as it shows that the general query log is not enabled.

When I click to enable it, and preview the changes, it appears to attempt to add "general-log" to my.ini - despite the fact that my 5.0 server does not recognize this option, and cannot start with it so defined.

This is critical, as it allows WB to configure options in my.ini which prohibit MySQL from (re) starting.

How to repeat:
Check "Enable General Log" using MySQL 5.0.

Suggested fix:
Do not write version-inappropriate configuration options.
[10 Feb 2010 12:59] Maksym Yehorov
WB now filters options which are not supported by server's version.
[17 Feb 2010 10:57] Maksym Yehorov
Fixed version detection
[1 Apr 2010 23:59] Johannes Taxacher
fix confirmed in repository
[19 Apr 2010 14:37] Tony Bedford
An entry has been added to the 5.2.17 changelog:

This bug occurred when using the MySQL Workbench Administrator with MySQL Server version 5.0. When selecting Enable General Log in the Administrator's configuration page, MySQL Workbench attempted to add the option general-log to the configuration file, even thought this is not supported by MySQL Server 5.0.