Submitted by pban02 on Mon, 03/01/2010 - 09:35 Pro Licensee
Currently the default MySQL setup uses the MyISAM Database engine and InnoDB needs to be configured manually by editing the my.cnf options file or by adding additional options files in /etc/mysql/conf.d.
Being able to do this in Virtualmin -> Systems Settings -> Server Templates or Webmin -> Servers -> MySQL would be a very useful feature.
TIA
Status:
Closed (fixed)
Comments
Submitted by JamieCameron on Mon, 03/01/2010 - 16:05 Comment #1
That's a good idea, I will make this editable at Webmin -> Servers -> MySQL Database -> MySQL Server Configuration , in the Webmin 1.510 release.
I'm not sure if using InnoDB is a good idea with Virtualmin though, as it by default puts all tables into one big file, and thus prevents domain disk quotas from applying to database files.
Submitted by sgrayban on Tue, 03/02/2010 - 00:51 Comment #2
I don't know of any maintained php scripts that use InnoDB anymore -- As Jamie said this creates one file instead and in the past this was proven to be a bad idea as there is no good way to recover or optimize the tables like MyISAM can.
Maybe this should be enabled as an advance feature because InnoDB isn't widely used anymore.
Submitted by pban02 on Wed, 03/03/2010 - 16:25 Pro Licensee Comment #3
Actually InnoDB is strongly recommended for MySQL sites that have a lot of writes and/or need transactional support. InnoDB is an advanced engine - it supports row level locking, whereas MyISAM locks whole tables when writing. It also has ACID support.
The next version of Drupal, Drupal 7 will start using InnoDB as the default engine and it is already recommended as the engine of choice for heavy duty Drupal sites.
InnoDB has many parameters that can be tuned. For details see: http://dev.mysql.com/doc/refman/5.1/en/innodb-configuration.html
It would be nice to have these supported in Virtualmin.
I am currently using a .cnf file in the /etc/mysql/conf.d directory to override the default settings in my.cnf.
InnoDB has an option to split the database among different files. There is an option called innodb_file_per_table which causes every table and its indexes to be stored in a separate file. For details see: http://dev.mysql.com/doc/refman/5.0/en/multiple-tablespaces.html
Submitted by JamieCameron on Wed, 03/03/2010 - 23:46 Comment #4
I'll add an option for innodb_file_per_table in the next Webmin release too ..
Submitted by Issues on Thu, 03/18/2010 - 01:20 Comment #5
Automatically closed -- issue fixed for 2 weeks with no activity.