RE: [PEAR-DEV] Re: [binarycloud-dev] FW: lets talk "metapear" - politics aside:-)

> -----Original Message----- > From: Alex Black [mailto:enigma@turingstudio.com] > Everything else about metabase, i.e. the API, loading, etc I think can be > either toasted and done over or tweaked until it's faster. I don't think > metabase will ever be as fast as ADODB (hock, spit), or PEAR:DB, because > it > does so much more. At the same time I think there is quite a lot of stuff > that could be done to make it a lot faster. Actually I think if we find a nice solution to separate metapear into packages then I think metapear can very well compete with PEAR DB in performance (I think PEAR DB probably has some overhead with their result object which if I got tomas right is not something that really did much for them). I don't know enough about ADODB. Obviously seperating everything into packages is very easy. But I would like the including to happen automagically somehow :-) > What do you mean by 2 wrappers? do you mean DBMS wrappers? > > Oh nevermind I kept reading, I get it. A BC metabase wrapper and a BC > PEARDB > wrapper? Yeah exactly. Allthough metabase does not really not a wrapper .. just a slightly modfied metabase_interface.php > Lukas, so far your decisions have been 100% sound. So while I agree with > you > about code review, at the same time I now completely trust your judgement. > So we'll give you feedback but don't let us hinder your progress. > > Do what you think is right, check in once and a while, and if you happen > to > miss something we'll fix it - a lot of people will use this :) thx :-) one thing to keep in mind though: my strengths are mostly in design and not so much in php coding as I am not all that experienced in php coding. So even though my ideas might be sound, my code could maybe use an experienced hand (if only to use php to the max). Anyways I also think that the pear error handling (with their error code abstraction) is the way to go (allthough Manuel does not quite agree there). But I guess that had to happen anyways if "metapear" was to be included into PEAR (which to me is the main reason for all of this). 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 _______________________________