MySQL Bugs: #3519: Changes to startup variables ineffective

Bug #3519	Changes to startup variables ineffective
Submitted:	20 Apr 2004 18:12	Modified:	11 May 2004 17:01
Reporter:	Chris Gorton	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Administrator	Severity:	S3 (Non-critical)
Version:	1.0.3 Alpha	OS:	Windows (Windows 2003)
Assigned to:		CPU Architecture:	Any

Description:
Applied changes to my.ini file were having no effect even after service restart.

Appears to be due to changes being simply appended to the my.ini file, mine had a section for [WinMySQLadmin] at the end so any changes were being applied to this section and were therefore seen as not relevant and ignored.

How to repeat:
Apply changes and view the ini file.

Suggested fix:
Quick fix for users is to use cut and paste.
Fix for developers is to account for the use of sections in the ini file

OK before you bite my head off I've just spotted that it does take sections into account! However because of another bug I've just reported (#3518) they only appear to be ineffective because the generated section heading by MySQL Administrator is incorrect.

A fix for that should correct this problem also.

Obviously I could also reinstall mysql into the root dir but I probably shouldn't need to.

Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at
    http://www.mysql.com/doc/en/Installing_source_tree.html