Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:45698
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 213.123.26.183 cause and error)
Message-ID: <4ACC6A92.40701@lsces.co.uk>
Date: Wed, 07 Oct 2009 11:16:50 +0100
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.8.1.23) Gecko/20090908 Fedora/1.1.18-1.fc11 pango-text SeaMonkey/1.1.18
MIME-Version: 1.0
To: PHP Internals <internals@lists.php.net>
References: <1254806557.19561.3.camel@samuel-laptop>	 <4ACBC540.4090308@beccati.com>	 <1254894205.7418.32.camel@samuel-laptop> <4ACC2B8F.2040302@oracle.com>	 <4ACC2E8F.8040903@beccati.com> <4ACC2F62.4050601@oracle.com>	 <4ACC30A3.8030205@beccati.com>	 <CB0E1D7C-7456-4A0F-8C53-A0F0B9F1425F@pooteeweet.org>	 <4ACC32E1.6070909@oracle.com> <4ACC3DDE.8020905@beccati.com> <fe05d1540910070117q10199101k2cdfbe290e82a33a@mail.gmail.com> <4ACC527A.8090909@beccati.com>
In-Reply-To: <4ACC527A.8090909@beccati.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] PDO PgSQL: _pdo_pgsql_notice
From: lester@lsces.co.uk (Lester Caine)

( Having stripped 6 people from the reply list ... )

Matteo Beccati wrote:
> Pierre Joye ha scritto:
>> Having them part of the PHP errors is counter intuitive and add extra
>> work for little gain. Mysql being the most cleaner way to do it at
>> this stage as it does not interfer with php code at all.
> 
> Yes. That's exactly why I added a new method, although driver specific.
> 
>> Could we make it independent from php's errors (be notices or
>> warnings)? For example to add a PDO statement method to fetch these
>> messages after having executed or prepared a query, getMessages for
>> example.
> 
> The PDO::exec(), method doesn't return a PDOStatement. With exec being
> the most common way to execute DDL or DML queries, the ones that are
> more likely to return a notice or warning.

Hopefully now we can get back to addressing the areas where PDO is 
simply not up to the job? I'm sure half of the reason that there has 
been no real rush to support PDO from some areas is simply because to 
many of the driver specific elements are missing, and saying that we 
just need to add them for each driver still seems wrong to me. Currently 
the best way to handle a specific database is it's own generic driver, 
and if using PDO, one normally ends up loading the relevant generic one 
when the holes start to appear? The database engines are getting more 
and more complex, and while PDO sort of provides a flat playing field 
for data (one with it's own holes ) it still has some way to go to 
provide a flatter interface to database extensions such as 'notice' ?

-- 
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk//
Firebird - http://www.firebirdsql.org/index.php