RE: [PEAR-DEV] unified db?

Renaming the entire OO API to match existing functions and reordering of parameters .. I have not looked at the specifics but there might of course we cases where an existing PEAR:DB function might not match etc. In those cases I will have to see what to do. :-) The direct use of the OO API is very new for metabase (a couple weeks) so I think the Metabase world can do fine with a wrapper to retain backward compatibility (there may have been some people that have actually made the switch already or that used some hacks). Since the old standard interface can easily be modified to call the pearified methods its actually quite easy to keep BC with both PEAR DB and Metabase at the same time. There will of course be a number of functions coming from Metabase that have no equivalent (I will try to come up with a new name or we discuss this on the list etc.) or where a method has more parameters (I will make sure that the parameter then is optional). There might be cases where I (we) decided that moving some PEAR DB feature to that Metabase core is not feasible (I don't have an example ready) in which case we will also have to add a wrapper for the old PEAR DB userbase. All in all this might turn out to not be all that difficult since we have an OO core and with the next release the main missing functions are being added (speaking of the bulk fetching). Its been well over a month of high stress programming since I last looked at PEAR DB but what functions (aside form bulk fetching) are in PEAR DB that Metabase lacks? I should probably sit down and do this research myself soon (hopefully Sunday evening as today is filed up with ultimate Frisbee and cheering for my friend - he is playing in the playoffs for the 1st german indoor field hockey league! - go eike!) In terms of documentation it will have to work with phpDoc (sp? .. there are several different ones iirc .. but I will of course use the one that is in the CS). Metabase comes with a nice testing suite and good documentation and tutorials. Depending how drastic the changes will be I think this could form the foundation of the future documentation. But I guess we will see once we now how far the final DB abstraction diverges (requiring wrappers to keep BC) from Metabase or PEAR DB. So please comment. I know there were other people involved in the last discussion. It would be nice to hear at least from all those people. 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: Paul Meagher [mailto:paul@datavore.com] > Sent: Saturday, January 05, 2002 4:43 AM > To: pear-dev@lists.php.net > Subject: Re: [PEAR-DEV] unified db? > > Lukas Smith wrote: > > > I do have time to pearify Metabase. > > I looked over the API of metabase. > > It is a clear API from what I can tell so far. > > I thought the prefix of Metabase on all the function calls was distracting > and made the function names too verbose (an API usability issue?). > > What about this: > > $mb->MetabaseGetBooleanFieldValue > > becomes the more PEAR like > > $mb->getBooleanFieldValue > > To convert the API to a PEAR naming style I think a general rule would be > to eliminate the Metabase tag and lowercase the first letter of the next > word. > > After the API conversion, I would then try see if PEAR::DB and Metabase > can > live harmoneously together in a deeper sense then just a common looking > API. For example, can the same $db object access PEAR DB methods and > Metabase methods. Adding some core Metabase methods first might work - > enough to demonstrate that metabase functionality is now accessible in > PEAR > DB in a useful fashion. I have no idea if this approach will work however > without doing more research on the matter. > > What did you have in mind for PEARifying Metabase? > > Regards, > Paul Meagher > > > 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 > > _______________________________ > > > > > > > > -- > > PEAR Development Mailing List (http://pear.php.net/) > > To unsubscribe, e-mail: pear-dev-unsubscribe@lists.php.net > > For additional commands, e-mail: pear-dev-help@lists.php.net > > To contact the list administrators, e-mail: php-list-admin@lists.php.net > > > > > > > -- > PEAR Development Mailing List (http://pear.php.net/) > To unsubscribe, e-mail: pear-dev-unsubscribe@lists.php.net > For additional commands, e-mail: pear-dev-help@lists.php.net > To contact the list administrators, e-mail: php-list-admin@lists.php.net