RE: [PEAR-DEV] unified db?

> Sorry to not answer before, this week I was terrible busy. About > pearifing Metabase, personaly I won't take part directly on that. I like > PEAR DB because is a modern library with clean code, a unified cool > error handling system, the eficient way it resolve abstraction problems > and also because the kind of people that form the core team, > contributors and users. So I prefer to continue supporting DB. > > What I could indirectly help on that is giving ideas on the new methods > or API modifications that this Metabase adaptation could need. I will > try to adapt the posible changes to PEAR DB if the people find them > good. > > I surely give my best wishes to that project and I will be very close > for tracking the progress. > > > Tomas V.V.Cox Ok, so you still want to stick with PEAR DB as it is and you want to continue to focus your efforts on PEAR DB as it currently is? In terms of clean code: Is this just about formatting or do you think that Metabase is flawed by its design from a programmers point of view. Formatting can be solved for "you" (since I would follow the PEAR CS) but the latter cannot since my proposal will mean taking the Metabase and how it is designed. What does this exactly mean for my proposed project? Will there be 2 DB abstraction layers in PEAR? How do you and the rest of the core PEAR developers feel about this? Best regards, Lukas Smith smith@dybnet.de _______________________________ DybNet Internet Solutions GbR Alt Moabit 89 10559 Berlin Germany Tel. : +49 30 83 22 50 00 Fax : +49 30 83 22 50 07 www.dybnet.de info@dybnet.de _______________________________