[TYPO3-dev] Moving pages in workspaces - brainstorm

[Dimitri Tarassenko]

Maybe this will sound stupid because it's so simple, but how about
using a separate MySQL database for each workspace? (as an option -
separate tables with a table name prefix). This way on the Workspace
switch in BE we just need to update $TYPO3_DB obj for most of the
tables except be_users and such, and instantly ALL existing extensions
support workspaces and everything works?

The easiest way to publish/revert then would be just to bulk copy all
tables between the databases. We may have harder time doing _partial_
publish when only some of the changes are published, but realistically
this is needed less often than moving pages and content.

If the problem with moving objects and pages is not solved I don't
really see that big of an advantage of workspaces vs. plain old
hiding/unhiding. There are some, but if there is no review/approve
workflow needed, they don't justify yet another thing users should
learn to manage content .

--
Dimitri Tarassenko