hi, On Wed, Oct 7, 2009 at 3:49 PM, Matteo Beccati <p...@beccati.com> 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 -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
