Re: ONE database abstraction layer

Aloha, let me introduce myself. I am Lukas Smith. We used to maintain our own DB abstraction layer and are now moving to metabase. In the process we also noticed that metabase rocks in terms of features but was not as nice to use as our old abstraction layer. Needless to say we still don’t want to go back :-) So we started doing some minor modifications (mainly in the fetch part so far) and we also want to make a couple advancements in terms of SQL function support etc. Maybe even do something as crazy as limited LDAP support (I am not deep into LDAP currently so really say if this idea is totally wacked), so that we can also easily switch between LDAP or SQL access to our user database (dream). Right now I am sort of swamped with work but in terms of core development to our framework I have DB abstraction on top of my list. So we were definitely about to make some suggestions in the form of real code to Manuel for metabase. I must admit I have not used any pear code so far, mainly because every time I looked to pear it did not really fit my needs (like in the DB example). Then again I like the general idea. I also assume that the coding standards are pretty good as from what I gather a bunch of smart people have worked on them. All in all it does seem to make sense to take the power from metabase and combine it with a nicer API and the support from pear (which would require going by the pear coding standards). ADO could also maybe be thrown into the mix. I will have sometime with my co-programmer today to look at this all (I hope). Best regards, Lukas Smith smith@dybnet.de _______________________________ DybNet Internet Solutions GbR Alt Moabit 89 10559 Berlin Tel. : +49 30 83 22 50 00 Fax : +49 30 83 22 50 07 www.dybnet.de info@dybnet.de _______________________________