Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:45692 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 79243 invoked from network); 7 Oct 2009 13:57:34 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 7 Oct 2009 13:57:34 -0000 Authentication-Results: pb1.pair.com smtp.mail=pierre.php@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=pierre.php@gmail.com; sender-id=pass; domainkeys=bad Received-SPF: pass (pb1.pair.com: domain gmail.com designates 72.14.220.156 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: pierre.php@gmail.com X-Host-Fingerprint: 72.14.220.156 fg-out-1718.google.com Received: from [72.14.220.156] ([72.14.220.156:50128] helo=fg-out-1718.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 36/0E-13083-D4E9CCA4 for ; Wed, 07 Oct 2009 09:57:34 -0400 Received: by fg-out-1718.google.com with SMTP id e12so865237fga.11 for ; Wed, 07 Oct 2009 06:57:30 -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=g2a43sAuh7La5yD5kX0XcjkJmnHZUBjX8GjhdTq8fTU=; b=wCjs8jMp41Oq48BRcWA9MArCo5fraqh1InT3GRf81UprheFzoxIUuAJY64yOkOXIoq 3dvWLmVW9UNyLYH99NjAgcsCSxhIV73bxqZAaJMaAoUaW1jvGsIA4+plvOnrlTO34ekb p9A1U3wRZ6MICjuVx/0HsFMlcIA62+NKwerVs= 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=Pl8414f4OAJ7VX5iD5m/jnJwhlHzp2V+0JPSJH4i8AhzHL8OMAsJVfr+ZlACbyJzpm RMa+wPStZJr7WHzG6B92IqNhw1DqxAg0nJtMwOM9A9UIm6URVvYMEKAGeVDmsHbqi6jL +yNLAo64gmdi88Wlu9gXlamNw7AFgQ34pxA1A= MIME-Version: 1.0 Received: by 10.86.232.5 with SMTP id e5mr7458fgh.27.1254923850703; Wed, 07 Oct 2009 06:57:30 -0700 (PDT) In-Reply-To: <4ACC9C53.9040200@beccati.com> References: <1254806557.19561.3.camel@samuel-laptop> <4ACC2E8F.8040903@beccati.com> <4ACC2F62.4050601@oracle.com> <4ACC30A3.8030205@beccati.com> <4ACC32E1.6070909@oracle.com> <4ACC3DDE.8020905@beccati.com> <1254914836.7418.52.camel@samuel-laptop> <4ACC9C53.9040200@beccati.com> Date: Wed, 7 Oct 2009 15:57:30 +0200 Message-ID: To: Matteo Beccati Cc: Samuel ROZE , Christopher Jones , Lukas Kahwe Smith , PHP Internals Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: [PHP-DEV] PDO PgSQL: _pdo_pgsql_notice From: pierre.php@gmail.com (Pierre Joye) hi, On Wed, Oct 7, 2009 at 3:49 PM, Matteo Beccati wrote: > By all means, I like the idea of a unified "message" API, but do we > really need the syntactic sugar (and development effort)? MySQL and > Oracle drivers can already access them with a standard PDO::query() > call. Only PgSQL notices require a special treatment because they are > currently discarded. > > I guess this is becoming more philosophical question: is the base PDO > class intended to only have common and portable functionalities Yes, and I consider this request as something we could have in a portable way. > Also I guess that mixing and matching names could be confusing: an > experienced Oracle developer using "dbms_output" would hardly imagine > that they can be fetched by calling getMessages() just by taking a quick > look to the documentation. Same goes for a Postgres developer who can > easily understand what pg_last_notice() does and would probably not > associate the familiar notice concept with getMessages. That's the problem when dealing with many databases. Messages can be confusing, notices could be better. In the end it is a documentation matter and if users do not read the manual (experienced or not) there will be no good name anyway ... :). -- Pierre http://blog.thepimp.net | http://www.libgd.org