[TYPO3-core] RFC #11916: Feature: New TYPO3_DB method for queries that expect just a single result row

[JoH asenau]

> I'm not OK with the change of $output as the phpDoc says it returns an
> array but in case of error, your change is back the same as v1, it
> returns an uninitialized variable. I know you did the same as in
> exec_SELECTgetRows but it's not optimal there either. I'd prefer
> having phpDoc telling us that it returns either an array or FALSE (or
> null) and then have $output initialized to FALSE (or null) before the
> error check. 

This change should be done in another RFC since it will influence other methods as well, that are currently using the same code. If this is going to be fixed, it should be done consistently but this doesn't belong to this single method.

Agreed?

Cheers

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