MySQL Bugs: #5846: Choice of default table type on WIN-installer

Bug #5846	Choice of default table type on WIN-installer
Submitted:	1 Oct 2004 12:35	Modified:	1 Oct 2004 13:20
Reporter:	David Powers	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Installing	Severity:	S4 (Feature request)
Version:	4.1.5-gamma	OS:	Windows (Windows XP)
Assigned to:	Michael G. Zinner	CPU Architecture:	Any

Description:
MySQL Server Instance Configuration Wizard 1.0.0 sets default-storage-engine in my.cnf to INNODB when choosing the Multifunctional Database option.

How to repeat:
There is no option to choose MyISAM as the default without completely disabling InnoDB.

Suggested fix:
It would be preferable to give users the option of choosing either MyISAM or InnoDB as the default table type, rather than imposing InnoDB arbitrarily. This is particularly important for inexperienced users, as opening my.cnf in Notepad is not possible from Windows Explorer.

The decision not to make MyISAM the default storage engine has been made on purpose. Especially in regards to new or not experienced users.

We found that it is very confusing for people that they only can use transactions when they use a specific storage engine. Therefore we decided to go with InnoDB as default table handler in a "Mulitfunctional Database".

The Config Wizard already features such a large number of pages that we would rather like to keep the number down.

But the Wizard will now use .ini files instead of .cnf files in the next release. That will make it easier to change the configuration file on windows by hand.

And Powerusers are encouraged to fine-tune the generated config file by hand.