Re: general questions

> layers. What I am proposing is to provide PEAR-DB users all Metabase > features right away without having them to drop PEAR-DB. Metabase Your are right, some metabase stuff is really cool. Especially I like the idea xml schema description, it would be a great benefit for PEAR, but not in PEAR::DB. Why? PEAR::DB is an unified API-Layer for SQL-based Relational-DBMS. But your xml schema isn't limited to this! Yor xml describes a data structure which can maybe stored in a file or a ldap-service too. So the xml scheme has to places in the data container layer, not in the physical container layer, like you want. For the get*FieldValue fetch*Result stuff for PEAR::DB, just write it! If it exists and keeps the coding standards and your are willing to maintain the enhancements, it will be commited!