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

[Ernesto Baschny [cron IT]]

Hi,

what makes the fe/be-group/users tables need to handle "concurrent
modifications"? I agree that *sessions tables are a candidate for InnoDB
 to avoid locking the whole table, we have it already there for
fe_session_data. But the users/group tables are pretty "static", and
could stay as simple MyISAM tables?

Or do you plan to change all tables to InnoDB in the end?

Cheers,
Ernesto

Oliver Hader wrote: on 25.06.2009 19:44:
> This is an SVN patch request.
> 
> Type: Bugfix
> 
> Bugtracker references:
> http://bugs.typo3.org/view.php?id=11251
> 
> Branch: Trunk
> 
> Problem:
> Some tables handling users and groups are still using MyISAM as database
> storage engine.
> 
> Solution:
> To serve concurrent modifications on the user/group tables with many
> elements, the database engine InnoDB should be used for the following
> tables:
> * be_groups
> * be_sessions
> * be_users
> * fe_groups
> * fe_users
> 
> olly
>