MySQL Bugs: #7312: multiple tablespaces forgotten

Bug #7312	multiple tablespaces forgotten
Submitted:	15 Dec 2004 10:01	Modified:	17 Feb 2005 17:06
Reporter:	Mickael Besson	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Administrator	Severity:	S2 (Serious)
Version:	1.0.17	OS:	Windows (Windows NT4)
Assigned to:	Alfredo Kojima	CPU Architecture:	Any

Description:

The multiple InnoDB tablespaces (.ibd) aren't settable since MyQSL Administrator.

On top of that, when you make modifications through MySQL Adm. and click Apply changes, and then Stop and Restart service : if 'innodb_file_per_table' was present in my.ini, it is between comments tag now ! 
So, some DB are stored in .ibd files and future others into ibdata (!).

How to repeat:

add innodb_file_per_table in my.ini or cnf after line '[mysqld]'
start service
create DB with InnoDB tables and add some records
look : there .ibd files have been created, so it's OK

Now open MySQL Adm. 
change something (ex : a buffer size or other)
->Apply changes (problem is here)
Stop and restart service
open my.ini
look, parameter is disabled : '#(Unknown option:)innodb_file_per_table'
After you can add another DB with InnoDB Tables and take account that no more .ibd files is created #-|...
very embarrassing.

Suggested fix:
read 'innodb_file_per_table' like a parameter since MySQL Adm.

Strange because in its first versions, the software permited to adjust this setting.

Please look at this. Finx

Works fine on SuSE 9.0, windows specific?

Thanks for reporting. We will address that a.s.a.p. 

The problem seems to be the mixture of _ and -. This one should work "innodb-file-per-table" but we have to correctly read in the other, too.

Hi

I cannot reproduce the problem on 1.0.19. What I did is to set 
innodb_file_per_table=1

in /etc/my.cnf, change something and save. The saved file correctly shows the option.
Now, when I change the option by hand as:
innodb_file_per_table=0
and then save something from Administrator, the option will be saved as:
#innodb_file_per_table=0
because 0 is the default value.

Can you please clarify whether you were expecting the option to continue being set to 0 (without being commented out)? Or were you getting a different result?

Thanks.

I can't reproduce it but I think that "innodb_file_per_table=X" wasn't recognized as a command (from MySQL Administrator only). Instead of that, we have to write "innodb-file-per-table=X", command that is recognized; and no more comments '#(Unknown option:)' are added...
Strange... 8[
This bug has surely been fixed in 1.0.19 version of MySQL Adm.

Thanks for checking! I'll close this bug and assume it's been fixed in 1.0.19