Blame | Letzte Änderung | Log anzeigen | RSS feed
** Introduction:PEAR MDB2 is a project to merge PEAR DB and Metabase into one DBabstraction layer.You can get info on these at:PEAR DB: http://pear.php.netMetabase: http://phpclasses.upperdesign.com/browse.html/package/20/At these URLs you will also find the licensing information on these twoprojects along with the credits.Actually MDB2 is the second major version of MDB.The main differences between the new MDB2 and the old MDB version isthat the API has been drastically refactored to clean up the APIand improve performance.If you have any questions or suggestions you can contact me (Lukas Smith)at this email address:smith@backendmedia.comCo-Author is Christopher Linn:clinn@backendmedia.comOr even better post a message to pear-dev@lists.php.net mailinglist fordevelopment related questions of the MDB2 package itself. For questionsusing MDB2 pelase direct your questions at pear-general@lists.php.net.** FeaturesMDB2 provides a common API for all support RDBMS. The main difference to mostother DB abstraction packages is that MDB2 goes much further to ensureportability. Among other things MDB2 features:* An OO-style query API* A DSN (data source name) or array format for specifying database servers* Datatype abstraction and on demand datatype conversion* Portable error codes* Sequential and non sequential row fetching as well as bulk fetching* Ordered array and associative array for the fetched rows* Buffered and Unbuffered fetching* Prepare/execute (bind) emulation* Sequence emulation* Replace emulation* Limited Subselect emulation* Row limit support* Transactions support* Large Object support* Index/Unique support* Extension Framework to load advanced functionality on demand* Table information interface* RDBMS management methods (creating, dropping, altering)* RDBMS independent xml based schema definition management* Altering of a DB from a changed xml schema* Reverse engineering of xml schemas from an existing DB (currently MySQL and PgSQl)* Full integration into the PEAR Framework* PHPDoc API documentation** Getting started:I would first recommend taking a look at example.php.This should give you a general feel of how to interact with MDB2.After that you may want to take a look at the rather large APIat www.backendmedia.com/MDB2/docs. There you will also find a documentdescribing the xml schema format and a little tutorial (it wasjust recently ported from Metabase, so it may contain errors).** Current State:The current release can be found at the PEAR webpage:http://pear.php.net/package-info.php?package=MDB2** Package Content:As a user the only php script you will need to include is MDB2.php which willinstall to your PEAR root directory. All other files and their containingclasses will be included via MDB2::factory(), MDB2::connect(), MDB2::singleton().These will load additional classes. Most classes are loaded on demand.Furthermore MDB2 provides an extensive testing framework that works through abrowser and command line interface. There are several other test that test thetwo wrappers. These files will install into your test dir found in thePEAR root dir.** Documentation:You can find the still incomplete documentation for MDB2 here:http://pear.php.net/manual/en/package.database.mdb2.phpPHPDoc generated documentation can be found at:http://www.backendmedia.com/MDB2/docs/The entire "public" API and most of the "private" methods (except for some ofthe lob classes) have been documented with PHPDoc comments. Most of the APIis borrowed from extPDO, so you can look there for detailed documentation.Since there are a large number of new methods available thanks to the Metabaseheritage of MDB2 you will also have to take a look in the Metabase documentation(which can be found at the URL mentioned above, but does require thatyou register with phpclasses). Most of these Metabase functions havebeen renamed and changed considerably. The main things left are the datatypesand the manager module.For example ($db being an MDB2 object):$converted_value = MetabaseGetTimestampFieldValue($database, $value);would now be$converted_value = $db->quote($value, 'timestamp');If you want to help out with documentation please email me.** Testing:For most of the tests you can set the username/password/hostname in the relevantconfig file. The user will need to have the right to create new databases.test.php/clitest.php/testchoose.php: Is the native testing suite provided byMDB2. Please see the README in the tests directory for details.example.php: Several test calls to MDB2's native API. It require PEAR::VAR_Dumppackage and are configured to use the following settings:username = metapearpassword = funkyhostname = localhost** How to write new Drivers:Skeleton drivers are provided in the docs directory of the MDB2 package.The best course of action would be to take a MDB2 driver and hack it to fitthe new RDBMS. This will surely be faster and it will ensure that the newdriver takes full advantage of the MDB2 framework. I would however recommendworking with the existing Metabase driver for inspiration that RDBMS whendoing those changes.In order to check compliance of the driver with MDB2 you can use the testingsuite (see the "testing" section above)** HistoryMDB was started after Manuel broad be into the discussion about getting thefeatures of Metabase into PEAR that was going on (again) in December 2001. Hesuggested that I could take on this project. After alot of discussion abouthow when and if etc I started development in February 2002.MDB is based on Metabase but has been reworked severely to better matchthe PEAR DB API and PEAR CS. The approach I have taken so far is to take DB.phpfrom PEAR DB and make it create a Metabase object. I have changed theMetabase structure slightly. The formatting has been reworkedconsiderably to better fit the final structure (MDB standalone with aBC-wrapper for Metabase and PEAR DB), to fit the PEAR CS and to make iteasier for other people to contribute.The metabase_interface.php was been renamed to metabase_wrapper.php andnow only serves as a wrapper to keep BC with Metabase. A wrapper willhave to be created for PEAR DB as well.Basically the result is a Metabase that is really close to the PEAR DBstructure. I have also added any missing methods from PEAR DB. Work onmoving the error handling to PEAR error handling is under way but stillneeds some work.In MDB2 the API was heavily refactored to be even more streamlined. Redundantfeatures have been removed. Some features where moved out of the core intoseparate loadable modules. Instead of resources resultsets are now wrappedinto objects similar to PEAR DB.** Credits (never to early for those huh? :-) ):I would especially like to thank Manuel Lemos (Author of Metabase) forgetting me involved in this and generally being around to ask questions.I would also like to thank Tomas Cox and Stig S. Bakken from the PEARprojects for help in undertstanding PEAR, solving problems and trustingme enough. Paul Cooper for the work on the pgsql driver. Furthermore Iwould like to thank Alex Black for being so enthusiastic about thisproject and offering binarycloud as a test bed for this project.Christian Dickmann for being the first to put MDB to some real use,making MDB use PEAR Error and working on the XML schema manager.Finally Peter Bowyer for starting the discussion that made people pickup this project again after the first versions of what was then called"metapear" have been ideling without much feedback. I guess I shouldalso thank BackendMedia (my company :-) ) for providing the necessary meansto develop this on company time (actually for the most part my entirelife is company time ... so it goes)