Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:45728 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 35768 invoked from network); 11 Oct 2009 19:08:38 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 11 Oct 2009 19:08:38 -0000 Authentication-Results: pb1.pair.com smtp.mail=mls@pooteeweet.org; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=mls@pooteeweet.org; sender-id=unknown Received-SPF: error (pb1.pair.com: domain pooteeweet.org from 88.198.8.16 cause and error) X-PHP-List-Original-Sender: mls@pooteeweet.org X-Host-Fingerprint: 88.198.8.16 bigtime.backendmedia.com Linux 2.6 Received: from [88.198.8.16] ([88.198.8.16:48011] helo=bigtime.backendmedia.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id D1/01-28660-43D22DA4 for ; Sun, 11 Oct 2009 15:08:38 -0400 Received: from localhost (unknown [127.0.0.1]) by bigtime.backendmedia.com (Postfix) with ESMTP id 6FD9E4144057; Sun, 11 Oct 2009 19:09:30 +0000 (UTC) X-Virus-Scanned: amavisd-new at backendmedia.com Received: from bigtime.backendmedia.com ([127.0.0.1]) by localhost (bigtime.backendmedia.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3JkKuiXLBx2D; Sun, 11 Oct 2009 21:09:29 +0200 (CEST) Received: from [192.168.0.151] (217-162-131-234.dclient.hispeed.ch [217.162.131.234]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: mls@pooteeweet.org) by bigtime.backendmedia.com (Postfix) with ESMTP id E2A594144009; Sun, 11 Oct 2009 21:09:28 +0200 (CEST) Cc: PHP Internals List Message-ID: To: Daniel Convissor In-Reply-To: <20091011155545.GA20206@panix.com> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v936) Date: Sun, 11 Oct 2009 21:08:29 +0200 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> X-Mailer: Apple Mail (2.936) Subject: Re: [PHP-DEV] Re: Patch: Use notices in PDO From: mls@pooteeweet.org (Lukas Kahwe Smith) 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 .. regards, Lukas Kahwe Smith mls@pooteeweet.org