RE: [PEAR-DEV] New Metabase Aniversary release

> Maybe, i didn't get your point. Do you want a db abstraction that looks > like > PEAR:DB but based on Metabase or a second kind of db layer in PEAR? The > second > part makes sense, but the first part not. There is no problem with having > two > db layers in PEAR with different requirements, but with two APIs doing the > same > based on different code base is ineffective. I want the thing that you say makes no sense :-) The idea (which was tossed around the pear-dev list for quite some time now) is to take the Metabase code, change the OO API (remember that Metabase comes with a wrapper by default, so changing the OO API will not force me to add another wrapper to remain backward compatible with Metabase - which I would also ensure) to match the API of PEAR:DB. The few missing functions from Metabase that have been implemented in PEAR:DB will be integrated into this merged version so if everything works smooth no wrapper for backward compliance with PEAR:DB (or if not only few things will be wrapped). The merged DB will be based on the core PEAR class and will follow the PEAR CS (hmm maybe I should put up a website with the proposal) and yes the idea is to unify the community behind this DB abstraction layer. I do not see a point in keeping to DB abstraction layers in PEAR if they both have the same API and basic approach (therefore not really offering anything but slightly different code). Of course this new DB abstraction layer will first have to be tested and there would surely be some time of coexistence within PEAR. 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 _______________________________