[TYPO3-core] RFC Bug #11251: Use InnoDB for user/group tables

[Ernesto Baschny [cron IT]]

Michael Stucki wrote: on 28.06.2009 17:37:
> Hi Olly & Masi,
> 
> Martin Kutschker schrieb:
>> Oliver Hader schrieb:
>>> * be_sessions
>>
>> Sessions are ever changing. That means that the InnoDB file keeps
>> growing and growing...
>>
>> There are some workarounds how you can reclaim the space, but I don't
>> think that all of users no them.
> 
> So the short answer is: Do not use InnoDB for be_sessions. :-)
> 
>> Do we have some information how to use InnoDB tables properly for our
>> users?
> 
> I think we don't need that. It should be used whenever it makes sense,
> and be avoided whenever it does not. Tables that change very often
> should therefore not use InnoDB but stick with MyISAM.

I fail to see the reason to use InnoDB if this were true. We changed
caching and session tables to InnoDB exactly because of their dynamic
nature: updating one record doesn't lock the whole table like on MyISAM.

In my eyes only the admin can decide whatever makes sense for his
environment. So instead of we shipping a mix of InnoDB and MyISAM
tables, I would prefer to have a global switch (in the installer) to
choose the desired engine and stick to that for all tables. The DB-admin
has to make sure that he has configured his innoDB engine correctly and
that he is able to work with it (i.e. configured it correctly, knows
about "extends", about the lost space, etc).

Cheers,
Ernesto