Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:45729 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 44959 invoked from network); 11 Oct 2009 20:32:48 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 11 Oct 2009 20:32:48 -0000 Authentication-Results: pb1.pair.com smtp.mail=lester@lsces.co.uk; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=lester@lsces.co.uk; sender-id=unknown Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 213.123.26.179 cause and error) X-PHP-List-Original-Sender: lester@lsces.co.uk X-Host-Fingerprint: 213.123.26.179 c2beaomr01.btconnect.com Received: from [213.123.26.179] ([213.123.26.179:14517] helo=c2beaomr01.btconnect.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id A1/00-44853-DE042DA4 for ; Sun, 11 Oct 2009 16:32:46 -0400 Received: from [10.0.0.5] (host81-138-11-136.in-addr.btopenworld.com [81.138.11.136]) by c2beaomr01.btconnect.com with ESMTP id EGH56311; Sun, 11 Oct 2009 21:32:34 +0100 (BST) X-Mirapoint-IP-Reputation: reputation=Neutral-1, source=Queried, refid=0001.0A0B0302.4AD240E1.012E, actions=tag Message-ID: <4AD240E1.20406@lsces.co.uk> Date: Sun, 11 Oct 2009 21:32:33 +0100 User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.8.1.23) Gecko/20090908 Fedora/1.1.18-1.fc11 pango-text SeaMonkey/1.1.18 MIME-Version: 1.0 To: PHP internals References: <1255038690.10759.9.camel@samuel-laptop> <1255120269.3605.14.camel@samuel-laptop> <1255122734.3605.21.camel@samuel-laptop> <4AD09F8B.1010205@lsces.co.uk> <1255195945.3605.49.camel@samuel-laptop> <4AD0D5CD.6030107@lsces.co.uk> <1255257805.3605.58.camel@samuel-laptop> <20091011155545.GA20206@panix.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Junkmail-Status: score=10/50, host=c2beaomr01.btconnect.com X-Junkmail-SD-Raw: score=unknown, refid=str=0001.0A0B0208.4AD240EA.01DB,ss=1,fgs=0, ip=0.0.0.0, so=2009-07-20 21:54:04, dmn=5.7.1/2009-08-27, mode=single engine X-Junkmail-IWF: false Subject: Re: [PHP-DEV] Re: Patch: Use notices in PDO From: lester@lsces.co.uk (Lester Caine) 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