Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:45846 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 53740 invoked from network); 20 Oct 2009 12:21:02 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 20 Oct 2009 12:21:02 -0000 Authentication-Results: pb1.pair.com header.from=samuel.roze@gmail.com; sender-id=pass; domainkeys=bad Authentication-Results: pb1.pair.com smtp.mail=samuel.roze@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.78.25 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: samuel.roze@gmail.com X-Host-Fingerprint: 74.125.78.25 ey-out-2122.google.com Received: from [74.125.78.25] ([74.125.78.25:59733] helo=ey-out-2122.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 95/82-39240-B2BADDA4 for ; Tue, 20 Oct 2009 08:21:01 -0400 Received: by ey-out-2122.google.com with SMTP id 22so1178180eye.39 for ; Tue, 20 Oct 2009 05:20:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=5igWDBq8ozfYQ19cf9ZSyFtvUrGO0IJYDdFtizjLB8I=; b=S335tmhl0eALBAmQpybZvplUqYZznYsIvYb4XMFKCGbLaJZp1H6jdC3igekmcr4jrm VPKUFMqc57HZpqoA0lvL9EYTOX67h5lO5UQlaVNA+MTcX+zqKwkh6hxK2yUIXSGlh+fI /3PemE2zZ0LeLOccFF19yaPY0WFA8BcQoss24= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=iJG3hiduJbJs7b37DtcUjcWsTjG2x47CYLQNyzGafq2iYUYAeuHRC/8xSaBre7ladL muhkr0HHu+50LDNlCSuFSHpU5+DUJDi/uJE0K2hefoJvovMh2d8aaxBfPkudxCSofTCK XazQcyvitCBHSbmPw/9mfM1pcKZisoz9b2H6c= MIME-Version: 1.0 Received: by 10.216.89.138 with SMTP id c10mr2288453wef.47.1256041256303; Tue, 20 Oct 2009 05:20:56 -0700 (PDT) In-Reply-To: <4ADCA8D4.5030006@oracle.com> References: <1255038690.10759.9.camel@samuel-laptop> <1255366822.3605.80.camel@samuel-laptop> <756DDBB8-0856-495F-B525-FD22C6EC7915@pooteeweet.org> <1255378394.4410.102.camel@samuel-laptop> <18e9608a0910130134l2d4768e5m282093d406268163@mail.gmail.com> <4ADCA8D4.5030006@oracle.com> Date: Tue, 20 Oct 2009 14:20:56 +0200 Message-ID: <18e9608a0910200520n41a820d4m69871c2366e06723@mail.gmail.com> To: Christopher Jones Cc: internals@lists.php.net Content-Type: text/plain; charset=UTF-8 Subject: Re: [PHP-DEV] Re: Patch: Use notices in PDO From: samuel.roze@gmail.com (Samuel ROZE) Hi Christopher, 2009/10/19 Christopher Jones : > The new interface combines system generated error messages with user > generated messages. I think you're talking about Oracle. > The original PostgreSQL example I saw seemed to use arbitrary text > messages, similar to Oracle's DBMS_OUTPUT (page 181 of > http://tinyurl.com/UGPOM). Page 191, this document explain how DBMS_OUTPUT raise informations, which can be got with the RFC's method. > The MySQL examples in the RFC are seem to > be similar to Oracle's compilation warnings (page 167 of > http://tinyurl.com/UGPOM). Page 177 there's a "PL/SQL Success With Information Warnings" paragraph. It talks about warning raised *only* by the Oracle system. It is like MySQL, you're true. The problem is that are you really wanted this warning ? I think that yes because it helps to debug, like others warning in MySQL and PostgreSQL. > I think two message types should be handled separately. Why not... But the problem is that execution time will increase because we'll have to exec two queries ! Why not because if we do that, we have to change the PDO::ATTR_LOG_NOTICES param. I don't really agree to that. Why not developp a Oracle function which will returns a compilation of these warnings ? It must be better ! Moreover, theses warnings / notices seens to be equal... Why differents methods to get them ? Regards, Samuel.