RE: [PEAR-DEV] Re: one abstraction layer (my proposal for)

> There's an English saying, > > "a bird in hand is better than two in the bush." > > No one knows what will happen. Go with what you are familiar and > comfortable with. That's the most important. Well the problem is that my company recently has made the decision that we don't want to support our own db abstraction layer because it is impossible for us to do the necessary testing and coding for every db. Right now we only use MySQL and our db abstraction layer was also tested under PostGreSQL. We just put together a server dedicated to mad testing. So we wanted to install DB2, Oracle, SAP DB, Adabas on there (I fear we can't use all of them in PHP simultaneous because of the ODBC driver). But for the testing I want to focus on my application and not on the db abstraction layer. Therefore, we want a db abstraction layer that is used by other people, like Metabase. There is no point in creating Lukas's metabase version. Obviously I want whatever we end up using to be the best there is. And I think we could add something to such a db abstraction layer. I just wanted to make clear under which circumstances I can offer what level of help. A side note: I emailed the dbx folks and they are using their dbx in production successfully. Also they have subscribed to this mailinglist now so I hope to soon see some insights from them (maybe I already have most of our C core db abstraction in place .. currently they only support MySQL and PostGreSQL going by the php manual). I will defiantly keep on following this discussion and I will keep adding my insights or idea, however useful they maybe, no matter what role in the actual coding process I will take. 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 _______________________________