Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:45757 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 34168 invoked from network); 12 Oct 2009 17:11:49 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 12 Oct 2009 17:11:49 -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:49825] helo=bigtime.backendmedia.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id CA/A0-54920-45363DA4 for ; Mon, 12 Oct 2009 13:11:49 -0400 Received: from localhost (unknown [127.0.0.1]) by bigtime.backendmedia.com (Postfix) with ESMTP id 769834144057; Mon, 12 Oct 2009 17:12:47 +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 oslVRM8p+GUU; Mon, 12 Oct 2009 19:12:46 +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 589784144009; Mon, 12 Oct 2009 19:12:46 +0200 (CEST) Cc: internals@lists.php.net Message-ID: <756DDBB8-0856-495F-B525-FD22C6EC7915@pooteeweet.org> To: Samuel ROZE In-Reply-To: <1255366822.3605.80.camel@samuel-laptop> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v936) Date: Mon, 12 Oct 2009 19:11:44 +0200 References: <1255038690.10759.9.camel@samuel-laptop> <1255366822.3605.80.camel@samuel-laptop> X-Mailer: Apple Mail (2.936) Subject: Re: [PHP-DEV] Re: Patch: Use notices in PDO From: mls@pooteeweet.org (Lukas Kahwe Smith) On 12.10.2009, at 19:00, Samuel ROZE wrote: > Hi, > > I'm writing here to take a point about the discussion. On one side, > you > want to turn this functionality to a global function, like it is > describe into this patch and on the other side, you said that on MySQL > and Oracle we can get this notices with queries so it is not needed > for > them but only for PostgreSQL. > > Before continuing every development I want to make like a survey about > what I (or we) will do. Here are my proposals: > > 1. Make this functionality only for PostgreSQL, with a "pgGetNotices" > function. > 2. Continue development for MySQL & Oracle, with the known that if > notices recuperation is enabled, PDO will have to do queries. > 3. Let development at this stage waiting that somebody else propose a > notices patch for other Database than PostgreSQL. > > Note: For MySQL there'is the mysql_info function > (http://dev.mysql.com/doc/refman/5.1/en/mysql-info.html) well .. what Pierre (and me supporting him) was asking for is to create an RFC page that details the actual sticking points with this feature so that they can then discuss the above points more if need be .. or we can take a vote on how to proceed. You are asking the general community to vote on something where there is no clear document describing the state of the discussion. Remember not everybody reads all messages and even I am likely to have forgotten a point raised in this thread by now .. and I have payed attention to this thread from the very beginning. Writing an RFC is not about making your life miserable .. and its not about stalling your request either. regards, Lukas Kahwe Smith mls@pooteeweet.org