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

Hello, Björn Schotte wrote: > > Hi, > > * Manuel Lemos wrote: > > > dictatorial way of "There's only place for the one and only > > > DB abstraction layer". > > Nobdoy is dictating anything, > > It seems to me that it is. It is a proposal and until somebody empowered to administrate PEAR says a definite yes, it will remain a proposal. > > If you only have one abstraction package that (almost) everybody uses, > > ACK. If... > > > This is why for Perl users to stick only to DBI, Java JDBC, Python > > Python-DB, Windows languages ODBC/ADO, etc... > > I agree with you on this, but if you look at (at least) > Perl, you see that there are plenty of DB abstraction > layers that co-exist inside CPAN. Of course the majority I don't see many abstraction layers. I see many database specific driver modules and many things that wrap around DBI. Anyway, DBI is the dominant database abstraction layer for Perl. > of users use DBI -- and I expect that the majority of PHP > users will end up in some years using only one DB abstraction > layer. But indeed that does not give anyone the right to say > "Because it will be one time in the future that everyone uses > Metabase, there's no right for PEAR::DB to exist anymore". > > For me, it's a very dangerous step. But the proposal is not to end with any abstraction layers, the proposal is to keep to PEAR-DB API wrapping it around Metabase so it can evolve quickly, then given the time it may evolve into something completely written in C for top speed. This will not prevent anybody from using or carry on developing the existing or even more abstraction layers for PHP. Regards, Manuel Lemos