Re: [PDO] Re: [PHP-DEV] [PATCH] New PDO methods for PostgreSQL driver
| From: | Lukas Kahwe Smith | Date: | Wed, 26 May 2010 06:08:03 +0000 |
| Subject: | Re: [PDO] Re: [PHP-DEV] [PATCH] New PDO methods for PostgreSQL driver | ||
| References: | 1 2 3 4 5 6 7 8 | Groups: | php.pdo |
| Request: | Send a blank email to pdo+get-403@lists.php.net to get a copy of this message | ||
On 26.05.2010, at 08:03, Lester Caine wrote:
> Wez Furlong wrote:
>>> I also did not say that we should not have driver specific additions
>>> > to PDO but if we do it, we actually need to discuss how we want to do
>>> > it. And this discussion has began (w/o much activities) on the PDO
>>> > lists.
>> I confess to being busy, but I don't recall any conversation where
>> this capability was revoked or otherwise called out as wrong.
>
> I think part of the point here IS the question of handling the use of features that AREN'T
> available to a driver. Currently people are quite happily writing PDO based code that can't be
> ported to any other databases simply in the way they use just the basic data abstraction. Adding
> another layer of functionality that can't be accessed generically is muddying the waters even
> further. If one is trying to port code to an alternate database, is it going to be necessary to
> build large switch arrays to select different functions from each driver? In which case ADOdb is a
> much more tidy way of handling things like this.
>
> +100 for adding DATA handling features in a way that it is at least POSSIBLE to implement them
> in other drivers if required?
I think Wez and Ilia are just expressing their paranoia over actually thinking about things instead
of just implementing the first thing that comes to mind. Obviously it makes sense to first think if
there is a sensible way to bring new functionality under a generic API and only if not then go with
a driver specific implementation (in which case it should be prefixed with the drivers name).
regards,
Lukas Kahwe Smith
mls@pooteeweet.org