[TYPO3-dev] Typo3 Performance
Martin Kutschker
Martin.Kutschker at n0spam-blackbox.net
Mon Mar 5 09:02:35 CET 2007
John Angel schrieb:
>> Because IMHO it was a bad move by the DB industry. As I see it the XML
>> hype forced them to add native XML support for queries. But if you think
>> about it, you'll see that querying XML needs more CPU power than
>> querying simple data types. We're just talking about improving
>> performance, not about wasting more CPU cycles.
>
> Of course, but you have to admit that FlexForm is excellent thing,
> giving you incredible freedom for making different types of content. But
> I am not using it because I cannot search through it using SQL.
>
> So, if we cannot make FlexForm be searchable normally, why not change
> its XML format to standard standard database table?
I think it was meant only for data that is needed for output, but not
needed for selections.
IMHO the idea of field reusing in tt_content wasn't that bad for
"selectable fields". It's just not flexible enough (think of the help).
Masi
More information about the TYPO3-dev
mailing list