[TYPO3-dev] New DB API function for queries that expect just a single result row
JoH asenau
info at cybercraft.de
Thu Sep 10 12:52:46 CEST 2009
Just to move this away from the thread that brought up this discussion:
>> And since he wants to keep his code clean and lean, I thought it
>> would be a good idea to put all three calls into one API function.
>
> You are welcome to optimize exec_SELECTgetRows() for a single row. It
> would take less time than arguing here :)
I still would prefer to introduce exec_SELECTgetSingleRow() to get rid of
the additional "if", since the developer already made the decision "if" he
wants a single row himself when calling the function.
Just like getRows() it will contain all necessary function calls to execute
the query, get the result row, free the result and return the data.
Any comments on this before I file a bugtracker entry?
Joey
--
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