[Typo3-dev] TemplaVoila, normalising the database and XML

[Frank Benkart]

I think this is a very small problem for the future of typo3. A much bigger
probelm is the TER. Look there and see all this extensions with bad
architecture. Putting all the code in one function for example. And look
there are a lot of them.

This is a quality problem!

"dan frost" <dan at danfrost.co.uk> schrieb im Newsbeitrag
news:mailman.1.1098719806.16510.typo3-dev at lists.netfielders.de...
> I've just found out how TemplaVoila stores the relationships to content
> records! (BTW: it's in pages.tx_templavoila_flex).
>
> Is this a good idea? It's a very strange way to do things because:
> - it's not normalised - the data help within pages.tx_templavoila_flex
> represents a non-existent many-to-many table...
> - as a result we experience the problems with import/export when
> tt_content records have different uids, so...
> - in order to change the relationships, you have to turn the contents of
> pages.tx_templavoila_flex into an array and edit it - i.e. it's not atomic
>
> There are almost certainly other reasons which all relate to general
> database normalisation principles.
>
> I mention this because the "extend tables forever..." philosophy is a
> really bad one. I don't want to be rude but: there are good reasons for
> database design principles.
>
> I realise that the world in going XML crazy - but i suggest that XML is
> a bad format in which to represent relationships. Of course, it's too
> late for TemplaVoila but I think these things should be known anyway.
>
> And don't get me started on tt_content...!!!
>
> dan