[Typo3-dev] the horror of different usertables

[Martin T. Kutschker]

Kasper Skårhøj wrote:
> On Mon, 2004-05-31 at 00:56, Elmar Hinz wrote:
> 
> BTW: Lets make a poll:
> 
> Who thinks the current "dual-user-table" is:
> - A "big wall" that is TYPO3s "weakest point": [YES] / [NO]

no

> Who thinks that merging the backend and frontend users table into one
> table is:
> - A good idea: [YES] / [NO]

yes, if it's an OPTION.

> - A top-priority (higher than planned core work): [YES] / [NO]

no

> If you answered "YES" to any of the above, do you want to:
> - Scan all (at least core) documentation for places where the
> frontend/backend users are mentioned and change the wording so it
> describes the new situation with a single table.
> - Write a converter utility that offers to merge the two tables in all
> existing installations when they upgrade.
> - Carefully analyse the core and most important extensions for the
> impact such a change would have including necessary patches to changes
> needed.
> - Carefully test the reliability of the new concept so you can convince
> sceptics that the new single-user-table is a very secure solution.

Hehe. Though I did answer yes I know that implementing any changes here 
is a big task. Not only big but risky as well.

The reason I answered yes once is I can see the point of those 
"community" guys. For "fun sites" it's a draw back. Though I think the 
weakest point for communities is the poor editing/input APIs (in 
comparison to the great BE/TCE-APIs).

Anyway, I don't want to move Typo3 to a single table setup in general. I 
favour a dual mode setup where the site admin is allowed to configure in 
the install tool whether to use one or two user types. But you can 
ignore my post as I'm certainly not want to waste my spare time of the 
next year on this task ;-)

Masi