TYPO3 Core

Any reason why?

We've got pages, fe_users, fe_groups, fe_sessions etc.

Or would you want to rename each of these as well?

Of course we can not rename the old ones for the obvious backwards compatibility reasons. However, along with database lessons and practices tables should be named in singular form.

You may also think in ways of ORMs where the class name matches the table name, then you would have a class called BeLayouts for example, where it should be BeLayout though.

Also I'm not sure whether it might not be just "layout".

It's not a big deal, I'll take care of it later, I just added the issue as a reminder...

"be_layout" would be ok, but "layout" wouldn't fit here, since there already is a "layout" field in the pages table and the naming would confuse people.

but maybe then we should use "backend_layout" to get rid of acronyms as well

sounds good to me

So... do it now or never?

now ;)
I'll prepare something

do you have something ready so that I can base upcoming bugfixes on the new naming - or should I just provide a patch with the current names?

committed to trunk (4.5) in r10200