Bug #19609 case sensitivity of innodb_data_file_path gives stupid error
Submitted: 8 May 2006 15:54 Modified: 22 Jun 2006 10:14
Reporter: Oli Sennhauser
Status: Closed
Category:Server: InnoDB Severity:S3 (Non-critical)
Version:all OS:any?
Assigned to: Marko Mäkelä Target Version:

[8 May 2006 15:54] Oli Sennhauser 
Description:
When MySQL was started with:
innodb_data_file_path = ibdata1:100M;ibdata2:50m:autoextend

instead of

innodb_data_file_path = ibdata1:100M;ibdata2:50M:autoextend

InnoDB was not started with this suppid error message:

060508 15:50:57  mysqld started
060508 15:50:57 [ERROR] InnoDB: syntax error in innodb_data_file_path
060508 15:50:57 [Note] /u00/app/mysql/product/mysql-5.1.9/bin/mysqld: ready for
connections.

I lost at least 1 hour at customer site and another our at home to find the reason.

How to repeat:
[mysqld]
innodb_data_file_path = ibdata1:100M;ibdata2:50m:autoextend

Suggested fix:
Make size value case insensitive (eas of maintenance?)
[8 May 2006 19:22] Miguel Solorzano 
Thank you for the bug report. Verified on Suse Linux and Windows XP.
[8 May 2006 23:05] Heikki Tuuri 
Assigning this little feature request to Marko. Should be fixed in 5.1.
[1 Jun 2006 12:12] Alexander Ivanov 
Pushed in 5.1.11
[4 Jun 2006 7:01] MC Brown 
Documented in the 5.1.11 changelog:

File size specifications for InnoDB data files were case sensitive.
[21 Jun 2006 16:16] Lars Thalmann 
This was pushed into 5.1.12.
[22 Jun 2006 10:14] MC Brown 
Moved to the 5.1.12 Changelog.