[TYPO3-50-general] Stable API for Persistence package

Jochen Rau jochen.rau at typoplanet.de
Fri Jul 17 14:29:07 CEST 2009


Hi Steffen.

>>>>> Or $query->execute($queryString)?
>>>>>
>>>>> To be honest, I'd try to keep it from existing...
>>>> I have to withstand a temptation. But without it, we will have
>>>> exec_SELECTquery in Extbase. Brrr!
>>>
>>> Why?
>>
>> Why what? (please mark)
>> - "withstand"
>> - "exec_SELECTquery"
>> - "Brrr!"
>>
>
> i have to admit that it sounds strange. Extbase is part of v4 core, but
> comes from FLOW3. i don't see a problem when extbase uses core mechanism
> of v4. I truly understand your wish of total abstraction, but some
> bridges has to be there. And "Brrr!" sounds like v4 is evil ;)

Let's face it: TYPO3 v4 is evil - evil good ;-)

"Abstraction" is not a goal for me, it is a way to achieve a goal. 
Namely to be able to semi-auto-port Extbase based extensions to FLOW3.

There is nothing bad about the methods of t3lib_db. And Extbase uses 
core functionality extensively. But all t3lib_db methods should be 
invoked inside the Storage Backend and not inside the Reposiories. I 
suggest to use the Query object as a wrapper/transporter for plain 
statements.

Jochen

-- 
Every nit picked is a bug fixed



More information about the TYPO3-project-5_0-general mailing list