Parts of it may but I believe there's some stuff which does need tighter
support from the DB driver and may require lower-level changes. In any
case, I suggest to look at this as a problem we want to solve; we can
even initially solve parts of it in PHP code if we want to. I personally
see no problem with an extension to also have some PHP code similar to
what SDO had. We don't need to create this artificial line if it doesn't
make sense or we want to do some stuff incrementally.

Bill Karwin and an IBMer did connect on this topic of Metadata because
we also needed it for Zend Framework so they could shed more light on
some of the ideas they had in this regards.

Andi

> -----Original Message-----
> From: Lukas Kahwe Smith [mailto:mls@pooteeweet.org]
> Sent: Monday, April 28, 2008 2:57 PM
> To: Andi Gutmans
> Cc: pdo@lists.php.net
> Subject: Re: [PDO] PDO version 1 improvements
> 
> 
> On 28.04.2008, at 23:08, Andi Gutmans wrote:
> 
> > - Full blown Metadata APIs ala JDBC (important for higher-level DB
> > layers).
> 
> > - A class for administrative functionality which can come in handy
> for
> > projects like phpMyAdmin.
> 
> For these two points I am wondering if these could also live in PHP
> userland. We have bundled PEAR code in the past, but none of the PEAR
> code was really aligned with the feature set we were planning as part
> of internals. I think stuff like this is tricky to really get right on
> all variations of databases so I think its better to keep them in
> userland to make it easier for end users to update (or even hand tweak
> things).
> 
> regards,
> Lukas