I don't know what any of the discussion, reasoning or intention is behind the INNO vs ISAM implementation on the server config. The "Add client" configuration makes it look like the server tells the client what table type to install, but my test client for 5.1 ISAM installs INNO tables. I don't know if I'm supposed to be modding my.cnf to set ISAM default, whether there's a bug that's supposed to make Drupal do it on the checkout's install, or what the core maintainers would like to have tested.

I'm just guessing at how to make them match, so here's a patch to make the server show 5.1 INNO instead of 5.1 ISAM.

CommentFileSizeAuthor
51_client_installs_inno.patch2.41 KBdeekayen

Comments

deekayen’s picture

deekayen commented

I guess it might be helpful for me to mention the client that installed INNO was Ubuntu 9.04 Jaunty. I got 5.1 from apt-get install mysql-server-5.1 instead of the regular mysql-server package.

deekayen’s picture

deekayen commented

see also #301362: Default to InnoDB in MySQL

deekayen’s picture

deekayen commented

Since 5.0 has ISAM and INNO, why doesn't 5.1 have both?

boombatower’s picture

boombatower commented
Status: Needs review » Postponed (maintainer needs more info)

Don't remember the original issue of discussion.

The idea was to test on 5.0 ISAM (fast and most popular first) as it will stop after any environment fails. Then hit the other two dbs...then test a 5.1 mysql (ISAM is faster) then make sure nothing weird happens on inno.

I am not sure what the point the patch is...the settings are there to instruct pifr what backend to use and on server what type of client it represents...they don't have anything to do with actual installation of Drupal 7...that needs to be setup whereever...default table type I don't know.

philipnet’s picture

philipnet commented
Component: Miscellaneous » Documentation
Status: Postponed (maintainer needs more info) » Active

@boombatower: then that needs documenting somewhere.

"Core now defaults to using MySQL's InnoDB storage engine rather than MyISAM."
see here: http://lists.drupal.org/pipermail/development/2009-May/033036.html

Suddenly the setting for MyISAM/InnoDB seem irrelevant.

deekayen’s picture

deekayen commented
Title: My 5.1 ISAM client installed INNO » Document somewhere that InnoDB will be default if my.cnf doesn't force MyISAM
moshe weitzman’s picture

moshe weitzman commented

i read that one should set skip-innodb in my.cnf so that tables get myisam for sure.

boombatower’s picture

boombatower commented
Status: Active » Fixed

This is documented on qa.drupal.org.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.