[TYPO3-english] Convert all tables to InnoDB

[Tomasz Krawczyk]

W dniu 2011-12-01 16:50, yanagik317 at netscape.net pisze:
> Thanks for those that replied.
>
> Barring the fulltext search comment, am I to gather this engine issue has to do with performance and not so much with "It's gonna crash Typo3 and it won't work"?  I've inherited this Typo3 install where tables like be_groups, be_users and tt_content are InnoDB but my fresh install had them in MyISAM.  I wondered if these were manually done from database side because somebody simply believed InnoDB to be "better" for whatever reason…  Since the site is "working OK" I'm inclined to keep the tables' engines the way they are (I have to work with DBAs who have their own opinions), but I wanted to get a general sense of how "messed up" this database might be from Typo3 standpoint.  Performance, for the time being, is less important than not breaking the site from the database's end.
>
> Not to deviate too much from the topic, but I'm seeing typo3conf/database.sql that seems to show up in the Database Analyzer when upgrading.  Move it out of the way (to like /tmp) makes that little section go away.  The concept seems to have been deprecated since beginning of 4.x or so, but is this something I'm better off not having when running the Install Tool?  I can always ignore, I'm good at that.
>
> Thank you,
> --Koji

In general it would be good to check default storage engine before 
beginning installation. F.e. WampServer has changed default storage 
engine in version 2.2. Now default db engine is InnoDB.

mysql> SHOW ENGINES;
+--------------------+---------+
| Engine             | Support |
+--------------------+---------+
| FEDERATED          | NO      |
| MRG_MYISAM         | YES     |
| MyISAM             | YES     |
| BLACKHOLE          | YES     |
| CSV                | YES     |
| MEMORY             | YES     |
| ARCHIVE            | YES     |
| InnoDB             | DEFAULT |
| PERFORMANCE_SCHEMA | YES     |
+--------------------+---------+
9 rows in set (0.00 sec)

Most extensions do not specify storage engine for their tables.

cheers
Tomek