Re: Re: PEAR DB abstraction layers
| From: | Lukas Smith | Date: | Mon, 19 Apr 2004 15:55:11 +0000 |
| Subject: | Re: Re: PEAR DB abstraction layers | ||
| References: | 1 2 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-28050@lists.php.net to get a copy of this message | ||
Stefan Neufeind wrote:
On 19 Apr 2004 at 15:45, Davey wrote: [...]Actually Stefan points out something which I for some odd reason forgot: Its really up to the DB maintainers to decide this anyways. I must be having some wierd attachment to long threads for having started it. However since its already there I might as well use the feedback to clarify the situation .. transparency and all :-) So I guess I will go back to the drawing board and do what I should have done from the start. Ask the DB maintainers if they agree to this. (Note I have discussed this topic with various maintainers of DB before but not with a clear roadmap or timeframe in mind). regards, Lukas Smith smith@backendmedia.com _______________________________ BackendMedia www.backendmedia.com berlin@backendmedia.com Linn Zwoch Smith GbR Pariser Str. 44 D-10707 Berlin Tel +49 30 83 22 50 00 Fax +49 30 83 22 50 07I'm very much +1 on this happening. A *lot* of new developers I see, are finding PEAR::DB and *not* PEAR::MDB[2]; this is simply because of the name. It is beneficial for new developers to be using MDB[2] because of the speed increase. I've yet to see somebody go back to DB after trying MDB[2] :)First of all, I must admit that I haven't yet used either MDB2 or DB very much. But from what I experienced and heard MDB2 seems really superior in a number of ways - although DB has a few more drivers, as Lukas pointed out. And since both packages follow the same approaches, it would imho be a good idea if the MDB2-people (actually Lukas) and the DB-people could pool their resources and bring up a new MDB2-class with some additions from the current DB. To me DB_v2 would be more obvious as *the* DB-package to use for the reasons already several times in this thread. The current situation is a waste of dev-resources in my eyes ... somehow both teams should find a way to cooperate.