Re: Adoption of Metabase (was Re: [PEAR-DEV]Re:Comparing ADODB with PEAR DB, Metabase andNative MySQL)

I'm just a regular PHP user, and I just want to toss in my comments. "Manuel Lemos" <mlemos@acm.org> wrote in message news:3BF9FB30.3070F1C@acm.org... > My most important point is end with just one database abstraction > package to let PHP developers write database independent applications, > just like other people do with other languages. It is silly that PHP is > different. I totally agree with this. One thing I hate is having several very similiar or identical solutions to choose from within PHP. I choose to use one method, a co-developer chooses a different approach, and then we argue for days which is best. It's such a waste. > > > cooperation. I don't mean to be harsh but if you want to cooperate try integrating > > I don't have the time or motivation to develop things for PEAR just > because it is funny to cooperate. I am no longer a college student so I > don't have plenty of free time to spare. What I do is because I need the > things for my job. If I am not selling what I do, I don't have a problem > with sharing. That is what I am doing with Metabase. > > One thing is certain, I don't want to go where I am not wanted. If there > is no interest in integrating Metabase in PEAR, fine. If not, I don't > have a problem with that. From the silence of PEAR core developers, I am > afraid there isn't much hope from their side to cooperate. At least I > made an honest attempt to cooperate. To me, as an objective user on the sideline, it looks like if the PEAR team are really eager to develop their own DB abstraction layer, which seems kinda silly considering the number of such layers allready out there. Why reinvent the wheel when you can port some already mature solution?! Metabase seems to offer what is needed, and has matured for two years right?. As a PHP user, I'm really eager to see something come out of PEAR, but the reluctance to adopt a good solution that I've seen over the past days here really surprises me and makes me wonder when I will see something useful come out of PEAR. But, whatever you choose to do, please DO NOT give us several DB abstraction layers to choose from, that would be very stupid and go against the whole idea of PEAR. Regards André Næss