Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:45707 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 11298 invoked from network); 9 Oct 2009 12:13:36 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 9 Oct 2009 12:13:36 -0000 Authentication-Results: pb1.pair.com smtp.mail=samuel.roze@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=samuel.roze@gmail.com; sender-id=pass; domainkeys=bad Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.218.206 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: 209.85.218.206 mail-bw0-f206.google.com Received: from [209.85.218.206] ([209.85.218.206:51822] helo=mail-bw0-f206.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id A1/A5-19113-FE82FCA4 for ; Fri, 09 Oct 2009 08:13:36 -0400 Received: by bwz2 with SMTP id 2so5845821bwz.23 for ; Fri, 09 Oct 2009 05:13:32 -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=HZ+MKUMIwTfK8IEtq0RXLb4Wk8rRqm/zIOO4b/TvT3M=; b=V1y2PdBAKZBp2fdaBBHNdLCWE7UUZr1G6bejZMSS7vwaKs6XLsFOEPe/cbeXTbZQT9 4ZDkRTJ8rbNHCOdrH9tzwB91RJ6/21ElehDVpW6jHTGbpCReTGJG54pQQ/HwSUpyYRys bZDdcHnqOYzV7VyWbuSzy66hQWhxh9WOK7RoA= 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=OAils1PlhSDLmSyTw1xcA/x+3mRohryOPaEwASz1InMjai4oDychmG+lc2nC0J3huY /OJ7YA0sv47/H+OlJs3TZaklKqL/wa93NkjmC0gg7+hYoTvTW+XCD9AVFx0Yl01vKswW D/Qc375ae91R2W5avbNzRNoTnI8/YET23aRGA= MIME-Version: 1.0 Received: by 10.204.8.65 with SMTP id g1mr2135562bkg.153.1255090412846; Fri, 09 Oct 2009 05:13:32 -0700 (PDT) In-Reply-To: <4ACF0A9F.3000804@beccati.com> References: <1255038690.10759.9.camel@samuel-laptop> <4ACE6613.808@oracle.com> <1255067917.4144.4.camel@samuel-laptop> <4ACED592.7070807@oracle.com> <4ACF0A9F.3000804@beccati.com> Date: Fri, 9 Oct 2009 14:13:32 +0200 Message-ID: <18e9608a0910090513v7e5e5084gf3fd7dcfb6b4ef06@mail.gmail.com> To: Matteo Beccati Cc: Christopher Jones , internals@lists.php.net Content-Type: text/plain; charset=UTF-8 Subject: Re: [PHP-DEV] Patch: Use notices in PDO From: samuel.roze@gmail.com (Samuel ROZE) > PDO::NOTICES_DISABLED > PDO::NOTICES_ARRAY > > to allow space for different formats (e.g. PDO::NOTICES_RESULTSET)? I not but what is the real interest of returning another type of data. And, what can be the other type ? It can have one notice as having many. > >> PL/SQL also has compile time warnings and errors that are handled >> differently, see "PL/SQL Success With Information Warnings" on p167. > > However, having read the above chapter, it seems to me that error code > 24344 with its warnings is more similar to MySQL warnings and PgSQL > notices. Which one should be automatically handled by PDO? I'd vote for > this one, leaving DBMS_OUTPUT still available by manually sending the > queries highligthed in your book. For your mind, PDO's Oracle driver have to catch the error #24344 to put it into notices and leave the user request Oracle database to have DBMS_OUTPUT's notices ? I disagree because DBMS_OUTPUT must be used in Pl/SQL functions, which must raise notices which are needed by the user... > > Cheers > -- > Matteo Beccati >