Hi Lukas,

I think some people have been caught up a bit too much in version
numbering. Changing the version number doesn't really change much either
way :) I guess the only thing a v2 would allow is making some backwards
incompatible changes if they were perceived to be beneficial. So I
suggest that either way we keep the version number out of the discussion
but discuss the delta of where we are today and what people would like
to see. The discussion was really about whether we can find a way to
make it easier for the vendors to contribute... they could also
contribute to 1.1 so I think it's been used more as fud then anything
else... anyway enough said :)

Some things:
- Make sure PDO classes implement interfaces so that frameworks can use
it as a generic data access interface and implement native driver
versions of it if needed (esp. PDOStatement).
- Full blown Metadata APIs ala JDBC (important for higher-level DB
layers).
- OCI8 has some persistent connection tuning parameters like timeout,
max_connections, ... Make that generic and consistent in PDO.
- Consider having an attribute that sets quoting style + maybe even
allow for a callback for quoting.
- Making quoting function aware of encoding in PDO (add quoting for
identifier & value)
- For consistency it would be good to clear errors on every call and
provide facility to expose multiple notices/errors that have occurred
within a transaction
- LOB only supports BLOB and not CLOB - Need ability to bind as
PDO::PARAM_CLOB
- A class for administrative functionality which can come in handy for
projects like phpMyAdmin.
- Test suite which DB driver authors can use for compliance testing.

Want me to update Wiki or are you doing it?
Andi

> -----Original Message-----
> From: Lukas Kahwe Smith [mailto:mls@pooteeweet.org]
> Sent: Monday, April 28, 2008 11:24 AM
> To: pdo@lists.php.net
> Subject: [PDO] PDO version 1 improvements
> 
> Hi,
> 
> I have collected a number of requests I have seen on various
> mailinglists, blogs and IRC chat conversations [1]. This does not
> include the pecl/internal bug database as of yet.
> 
> PDOv2 seemed to have been mostly driven by legal (licensing, copyright
> and patents) and internal (call back infrastructure not working so
> well for all drivers) needs. The purpose of this RFC is to collect
> what people feel that is missing from PDO in terms of what end users
> are asking for. The result of this RFC can either expose additional
> reasons for going towards a version 2 or show that there is still
> plenty of stuff to do in the current version 1. This could also be an
> opportunity for the various companies that showed an interest in PDO
> version 2 to get their feet wet in the PHP world without having to go
> down to the deeper and legally more tricky areas (of course twitchy
> lawyers might still prevent anything from happening before the
> required legal infrastructure has been put into place).
> 
> Anyways feel free to add to this RFC or point me at whatever you all
> of seen, read or experienced first hand that you feel needs to be done
> in PDO.
> 
> regards,
> Lukas
> 
> PS: I am posting this only to this list for now just to see what kind
> of discussion we will get on this list. Currently I am not yet sure if
> this list is really a good idea or if PDO discussions should be
> brought back to internals@. Lets see ...
> 
> [1] http://wiki.php.net/rfc/pdov1
> 
> --
> PDO Working Group Mailing List (http://pdo.php.net)
> To unsubscribe, visit: http://www.php.net/unsub.php