RE: [PEAR-DEV] unified db?

Well we should hold off until the next release for benchmarks because the next release will include bulk fetching as was mentioned in the release information of the last metabase release (actually one function call will be able to send the query, fetch the results, and convert any of the returned data if needed - of course this can also be done step by step). There will be other stuff in there as well but Manuel is the best person to ask for this. But let's hold off with discussing these new features until the next release because I know otherwise this thread will degenerate into a flame war again. I think with the next release Metabase should have overcome pretty much all of the (major) criticism. I was mainly looking for comments on the new OO interface. I want to hear if people think that this is the direction where they can deal with Metabase forming the basis for the new DB abstraction layer. If yes I will try and make some time available to pearify Metabase after the next release. I will definitively not want to work on something that will start off with fewer features than Metabase. We have actually already started our port to Metabase in December in my company so right now I have 2 abstraction layers in my system (Metabase and our old proprietary db wrapper) and I want to clean this situation up ASAP (with the new Metabase or a pearified Metabase). If not then I will focus any future development on Metabase. Of course this will not prevent of taking up whatever merging whatever opensource DB abstraction layer they see fit to form the basis of a full featured DB abstraction layer 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 _______________________________ > -----Original Message----- > From: ssb@kirin.trondheim.fast.no [mailto:ssb@kirin.trondheim.fast.no] On > Behalf Of Stig S. Bakken > Sent: Friday, January 04, 2002 12:15 AM > To: Lukas Smith > Cc: pear-dev@lists.php.net > Subject: Re: [PEAR-DEV] unified db? > > Lukas Smith wrote: > > > > Hello, > > > > well discussion has died down > > I know for sure that some people have already given up on the project of > > merging Metabase and PEAR DB > > I for one was defiantly not happy with the plan or the general results > > from the discussion. > > > > Anyways I still think it would be a good thing (tm) > > > > I have submitted some code to Manuel which will be added next to a bunch > > of other stuff in the next release, but Manuel has already made a new > > release that adds and OO interface to Metabase > > Are people getting happy with the structure of Metabase now? > > > > The next release will also add bulk fetching to improve performances. So > > this will then be there also. > > > > Well I guess you all know what I am driving at: Are people still opposed > > to pearify Metabase and make this the new PEAR DB abstraction layer? > > If people are now ok with it: What changes or added features are needed > > to not make the PEAR DB userbase unhappy? > > 1) coding standard compliance > > 2) .? > > How is the performance of Metabase's OO interface? Could you run the > benchmark used previously to compare pear/metabase/adodb on it? > > In principle, I don't mind replacing the inner workings of DB. But I > can not make a decision without more details. I'll go and familiarize > myself with Metabase's new OO interface, and maybe you could post what > you have in mind? There will probably be some API changes, which ones > do you see coming? > > - Stig