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

> 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. No program based on PEAR components is really interoperable at the moment. ;-| You mentioned the right point comparing templates vs. db layer. We decided to support two types of template system in PEAR based on the requirements - a lightweight (IT) and a heavyweight (maybe Smarty). At the moment PEAR::DB is just a unified API, not a unified SQL Layer. Metabase is prepared more then PEAR::DB for SQL independent stuff. I see no problems adding a pearized Metabase to PEAR, due to to different APIs, sourcecode and requirements. PEAR::DB and PEAR::Metabase could be equivalent to PEAR:IT and PEAR::Smarty