Re: [binarycloud-dev] Re: [PEAR-DEV] Re: [metabase-dev] RE: [PEAR-DEV] New Metabase Aniversary release

> Why not? People can choose if they want to use PEAR::Metabase > or PEAR::DB or PHPLIB's db class. precisely because much of the point of pear is to promote compatibility. again, because a database abstraction layer is a foundation component of any application, using APIs that are slightly different is a bad thing. >> _If_ that happens I think we are all better for it: we gain both the good >> api and the mature package... > > Why not PEARifying Metabase and giving a handsome wrapper that > behaves like PEAR::DB API? Because by definition it must have a superset of the methods available in the current PEAR::DB API because it is a more capable package. One database abstraction layer is all that is necessary. By all means have 15 different template engines, but do not have 15 different database abstraction layers: if we are to have interoperable code, we must have a single database abstraction package. _alex