[Typo3-dev] RFC: TYPO3, Kickstarter and M-M database relations

[S. Teuber]

Hi Martin,

> You would either clutter up tt_content_ext or would get lots of 
> additional tt_content_ext_* tables.
> 
> The former would give you no performance gain, because the table would
> have to joined with tt_content for normal content rendering.

Not if there is some "logic" that determines if additional extension 
fields are needed at all. But then we'd propably have to distinguish 
extensions that add something to a regular content element (except 
"insert plugin") from those that add completely new, own elements... I 
see that the whole issue needs some more fundamental thinking, but I'd 
rather not drop it lightly.



> Use flexforms if you need more fields if you're worried about the
> number of fields in tt_content.

It's not about what *I* do, since most of the frequently used extensions 
aren't maintained by me - schade eigentlich ;-)

Besides, I dislike the fact that a flexform field needs to be parsed to 
get to the actual data. If I got, say, 4 "items" like "view", "sort by", 
"sort order", "categories" (yes, these are taken from tt_news ;), I'd 
rather store them in 4 fields than in one field using XML - for easy 
access without the need for an XML parser. After all, TYPO3 may not be 
the only application using the database structure. 

Gotta admit that flexforms are really cool in the TCEforms, though. ;)

Sven