[TYPO3-dev] The extbase dilemma

[Maximilian Kalus]

Hi folks,

Xavier Perseguers:
> I have an example of small dataset which results in a non-acceptable 
> generation time.
[snip]
> Pretty "dumb" isn't it? But it was WAY too slow with the domain model 
> and Fluid. I ended up writing the optimized query using plain old 
> t3lib_DB methods, preparing an array of data (no objects) that was 
> passed and then consumed by Fluid.

Using other frameworks I have fallen back to plain old SQL occasionly,
because that would speed up certain queries by... well, very much. I
find it perfectly reasonable to use SQL sometimes, even though
frameworks try to shoo you away from it. There are queries that are very
hard to build and/or ineffective when using a framework query builder.

I think it is a practical thing of Extbase to actually create Repository
objects. You then have the freedom to decide on how to store and
retrieve your data. Using the query engine is just one (and preferred)
methods to do so - you could also serialize your models to files, use
t3lib_DB or get XML data from a remote source, if you like. The freedom
is yours and I think it is perfectly acceptable to stray from the
"prefered" method in this case.

Max.