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

Hi, * Alex Black wrote: > precisely because much of the point of pear is to promote compatibility. > again, because a database abstraction layer is a foundation component of any Template classes are also foundation components of modern applications. > application, using APIs that are slightly different is a bad thing. Of course, but no one forces you to do that. I, as a developer, can choose if I want to use PEAR::Metabase in my application or PEAR::DB. Remember, PEAR ist not Midgard. PEAR is no application framework. It's a pool of classes that follow coding standards. > One database abstraction layer is all that is necessary. I definitively *DO NOT* agree with that. -- PHP-Schulungen in Frankfurt und München! Mehr Informationen? >>> mailto:bjoern@thinkphp.de