[TYPO3-dev] Request for cleanup of typo3 database schema

[Martin Kutschker]

R. van Twisk schrieb:
> 
> I might be old fashioned, but it's really old fashioned that an 
> enterprise CMS uses MySQL by
> default with MyISAM storage (which was recently changed to InnoDB) and 
> cannot
> handle at least 2 or 3 other big RDBM's out of the box (Oracle, MS-SQL, 
> PostgreSQL)
> without hitting quite a number of roadbumbs to get it resolved and a 
> huge speed
> impact because of the use of AdoDB and other translation layers (DBAL).
> 
> The CR tries to solve that which is a good thing.

So does DBAL. There are many ways to move the burden of writing DB 
specifc SQL queries from the developer.

But I'm complaining when JCR reqires Xpath support and TYPO3 solves this 
by emulating it. If your app needs Xpath then choose a DB that supports 
it. THe JCR may have an API for that fine, but in case the DB doesn't 
have it, it should simply throw an error.

The Xpath feature could be detected at runtime with a capability API call.

> However I also do agree that we need to have a good API for Db access in 
> a fairly transparent way
> and RAW way. This to access external databases and to handle data that need
> raw speed of the DB. Like the last XX of data YY problems. Something a 
> CR might not always be able to solve quickly enough.
> 
> What other options do we have for JSR-170?
> We need at least:
> 
> CMS specific:
> 1) A concept of worksspaces
> 2) A concept of versions
> 3) A concept of history
> 4) A concept of multi-langual
> 
> Web specific:
> 1) A concept of multi-domain
> 2) a concept of user and group rights
> 3) A concept of time rights.
> 4) Caching mechanism
> 
> Just to name a couple that crosses my mind...
> 
> If we make the above with 'RAW' SQL,
> so that every extension is responsible for the above and properly other 
> items.
> Then I can promise you we will gain no step into the feature then we are 
> right now.

IMHO many extensions are "list type extensions". They do have single 
items, but many views are lists. As they usually come with relations and 
stuff SQL is fine to handle such stuff. Will JSR-170 store tt_news item 
in flat files? I have been told: JSR will know best how to handle this. 
I doubt that. How much AI shall this wonder thing have built in?

Masi