[Typo3-dev] Future of Typo3 - Aftermath

[Daniel Brün]

Hi Folks!
Hi Kasper!

Phew! That has been some rough stuff here on the list. What has it 
tought us?

a) keep on going
b) eventually add some points to the to-do list
c) enjoy an already VERY, VERY GREAT system
d) never forget that this is not a commercial solution: you don't buy 
stuff you don't like. Don't like Typo3? Just don't use it... simple, eh?

Here's just the single point of the discussion that I would like to 
comment on:
Basically, DB-normalisation is a great thing.
It makes a huge DB-system very, very modular and smooth.

BUT: With data spread over many tables, lots of joins are necessary to 
collect a set of data that actually belongs together, thus definitely 
impairing performance. Even though normalisation is great in science, in 
daily use applications it's not always the way to go.

My suggestion is to find a decent way between those two paradigms (one 
huge table against a couple of normalized ones).
I don't think it makes any sense to completely normalize the system 
down, but maybe one could split some tables where it makes sense?

In the content-table a couple of rows come into my mind, that could 
better be placed in some kind of attribute-table containing only 
key-value pairs. just a thought.

Anyhow, as there is currently some work done regarding DB-abstraction, 
maybe one could to some normalization in the same go?

I am willing to help out in DB design and optimization, just let me know!

Cheerio,

Dan