[TYPO3-dev] Update database when saving plugin flexform configuration in BE?

JoH asenau info at cybercraft.de
Thu Sep 10 05:42:44 CEST 2009


> first: there is an API for a reason: you should use it. There are so
> much things you may forget like translations, versions etc. so you are
> safe using the API.

exec_SELECTquery, sql_fetch_assoc and sql_free_results are API functions
too, aren't they?

> And there is no significant difference between a one-time-loop and a
> single call.

Besides the unnecessary function calls there is a difference - even if it
doesn't seem to be significant -  since the one time loop gives you the row
as subarray of blah[0] instead of a simple array. You get an unnecessary
array just to split it up again.

> When we talk about performance we should concentrate on the real
> performance issues which definitive exists like determineId in FE

During the performance meeting we had with Rupi in July, we found out that
just replacing the unnecessary API function calls that have been implemented
into the so called caching framework, with the appropriate ones (still API
functions) definitely had an impact on the overall performance of the FE
output. So I guess this might be true for the rest of the core as well.

BTW: My first comment was intended as kind of a joke, but it seems there's a
grain of truth in the heart of it ;-)

Cheers

Joey

PS: We will check our own extensions as well and remove unnecessary or
inappropriate stuff within the next releases.

-- 
Wenn man keine Ahnung hat: Einfach mal Fresse halten!
(If you have no clues: simply shut your gob sometimes!)
Dieter Nuhr, German comedian
Xing: http://contact.cybercraft.de
Twitter: http://twitter.com/bunnyfield
TYPO3 cookbook (2nd edition): http://www.typo3experts.com
TYPO3 workshops: http://workshops.eqony.com






More information about the TYPO3-dev mailing list