Lukas Kahwe Smith wrote:
On 11.10.2009, at 17:55, Daniel Convissor wrote:
If the notice/warning gathering abstraction is going to be sending
queries to the DBMS in the background, one needs to be careful about
maintaining both the results and metadata from the original query that
caused the warnings.
hmm why do you think that PDO would need to take special care about
this? seems like this is the job of the PDO using code ..
but it does raise one concern that i did not think about before: one
potential issue is that with unbuffered queries (which are on by
default) in MySQL you can only have one open result set at a time, so
you cant check the notices until you have fetched the result set .. then
again notices are usually only for insert/delete/update ..
This was part of what I was trying to highlight. That and the fact that
people who use databases where these sorts of activity is NORMALLY
handled by additional SQL queries will not be looking for an 'old
fashioned' method of returning them? And people writing code for Posgres
then trying to run it on MySQL should not expect it to work anyway since
any information returned is most certainly going to be different.
--
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk//
Firebird - http://www.firebirdsql.org/index.php
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
