[TYPO3-core] SELECTquery() vs exec_SELECTquery()

[Karsten Dambekalns]

Hi.

On Thursday 01 June 2006 15:54, Martin Kutschker wrote:
> Hmpf, so I cannot write the statements I like (even *with* the API) because
> of DBAL doing such super-fancy stuff like mapping tables to handlers.

Well, when in life one can have everything at once? :)

But the only thing you cannot do right now is fetch the query first and 
execute it later, right? Or did I miss something else?

> But wait, perhaps we can get a EXECquery() method.

I am still not sure whether we should go *that* extra mile, just to make this 
possible. I'd rather invest the time to make the exec_*() methods cache 
queries they already saw, and avoid parsing/mapping them again...

> If SELECTquery would not return a string, but an array/object it coud be
 ...
> The result of prepare_INSERTquery should contain the SQL statement, the

Yeah, this would work. As I said earlier, this seems to be something for 5.0, 
and for that I even think that *maybe* SQL should be abandoned alltogether...

Karsten
-- 
Karsten Dambekalns
TYPO3 Association - Active Member
http://association.typo3.org/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 307 bytes
Desc: not available
Url : http://lists.netfielders.de/pipermail/typo3-team-core/attachments/20060602/f6eab471/attachment.pgp