RE: Re[2]: [PEAR-DEV] Framework Development (2)

Hi, yeah MDB takes care of alot more abstraction then PEAR DB does. It abstracts types (btw: it does not use mysql TIMESTAMP) and tons of other stuff as well (like REPLACE, LOBs and even limited sub queries). And the xml schema system also allows easy moving between DB's. Anyways it's definitely in a state where it can and SHOULD be tested. The only draw back is that currently MDB only supports mysql. But this limitation could be quickly lifted by porting a Metabase driver (there are instructions in the MDB cvs dir: Readme.txt). Internally the API is modelled heavily after PEAR DB (it does not use a result object however). So moving to MDB should not be hard (actually you can use the MDB-PEAR-DB-Wrapper as a first step). Best regards, Lukas Smith smith@dybnet.de _______________________________ DybNet Internet Solutions GbR Reuchlinstr. 10-11 Gebäude 4 1.OG Raum 6 (4.1.6) 10553 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: Martin Jansen [mailto:mail@martin-jansen.de] > Sent: Monday, June 17, 2002 7:20 AM > To: rocha@i-node.com.br > Cc: pear-dev@lists.php.net > Subject: Re: Re[2]: [PEAR-DEV] Framework Development (2) > > On Sun, 16 Jun 2002 17:29:07 -0300 (BRT), Sebastiao Rocha wrote: > > >> "Martin Jansen" <mail@martin-jansen.de> wrote*: > >> > >> On Sun, 16 Jun 2002 22:07:26 +0200, Jens Fischer wrote: > >> > >>>Currently I use the old PEAR DB classes for database access, since I > >>>haven't tried out MDB, yet. I am using a MySQL backend for testing, but > >>>moving to another DB should be no problem due to PEAR DB. > >> > >> FYI: Don't rely on PEAR DB too much when it comes to database > >> abstraction. PEAR DB provides a unique API for a lot of different > >> database engines, but it does not work around specific features that > >> are only available in a specific engine. Anyways, if you only use > > > >What are the choices we have then? MDB? I understand that the main work > >is being done on the merge with Meta Base. > >Will this solve the problems with database abstraction? > > MBD will incorporate the features of Metabase, which should support > more abstracting features than PEAR DB. (I can't tell it excactly, > since I don't use Metabase.) > > - Martin > -- > Martin Jansen, <mail@martin-jansen.de> > http://www.martin-jansen.de/ > > > > -- > PEAR Development Mailing List (http://pear.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php