Got it. Clear now. See here: http://dev.mysql.com/doc/refman/4.1/en/converting-tables-to-innodb.html "The fastest way to alter a table to InnoDB is to do the inserts directly to an InnoDB table. That is, use ALTER TABLE ... TYPE=INNODB, or create an empty InnoDB table with identical definitions and insert the rows with INSERT INTO ... SELECT * FROM ...." Seems a script with show tables, then alter table does the trick. InnoDB involves creating a table space a la Oracle though, so there is more preparatory work that has to be done. On 12/30/05, Bèr Kessels <ber@webschuur.com> wrote:
Op vrijdag 30 december 2005 15:58, schreef Khalid B:
I think I was not clear enough. What I meant was I do not think making InnoDB the default for Drupal will not be a good idea, since only the very high traffic sites that experience locking contention suffer from this.
I think /I/ was not quit clear. From what I heard, using myISAM is the best option for Joe Schmoe. But it also seems that some people will need innodb. Hence I want to ship my drupalCOM with a simple script that allows anyone to "change gears" (change to innoDB withoout having to jump trough hoops) if need arises.