RE: [PEAR-DEV] SQLite and PEAR DB

Hi, that would of course be very cool. ATM there is only a mysql driver for MDB and someone is working on a pgsql driver. I don’t know much about SQLite but normally I would recommend people working from an existing Metabase driver. Unfortunately there isn’t a SQLite driver for Metabase so it might be a bit more difficult to create a driver. Anyways MDB is really in the final stages before the 1.0 release. For the most part I am just doing little clean ups, bug tracking (mainly in the error handling) and documentation work. If you were to write a driver it would obviously help in ironing out the last little kinks that still exist. 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: Jonas Koch Bentzen [mailto:test@understroem.dk] > Sent: Monday, June 17, 2002 5:50 PM > To: pear-dev@lists.php.net; ssb@fast.no > Subject: Re: [PEAR-DEV] SQLite and PEAR DB > > Stig S. Bakken wrote: > > On Sun, 2002-06-16 at 17:57, Jonas Koch Bentzen wrote: > > > >>Has anyone begun work on a SQLite class for PEAR DB? I'm thinking of > >>making one, but of course I'd like to know if anyone has done some of > it > >>already. > > > > > > Not that I know of. If you want to start working on it, please apply > > for a CVS account at http://www.php.net/cvs-php.php and a > > PEAR account > > at http://pear.php.net/account-request.php > > Hi Stig, > > I have a couple of additional questions: > > Seeing how MDB will eventually replace DB, should I opt to write the > class for MDB instead of DB? > > Do you have any suggestions for how to construct the DSN? SQLite is kind > of special when it comes to connecting: Instead of specifying the host, > the username, etc., you specify a file (the whole database is contained > in one file). If the file does not exist already and you want SQLite to > create it with certain permissions, you can also specify the permissions > (e.g. 644). The problem is the fact that the path to the database file > may contain slashes (in most cases it will), but the different parts of > the DSN are also separated with slashes. Another problem is the > permissions part - there no logical place to put it in the DSN. Do you > have any idea as to where I could put it? Otherwise, I'll just leave > that portion out (i.e., not allow the user to create a database with > custom permissions). This is my suggestion for a DSN - please let me > know if it fits in with > the way you've designed DB: > > sqlite:///home/user/test.db > > Another question: Most likely when I've written the class and tested it > thoroughly, I won't have the time in the future to maintain the class. > Would it be okay to make the class, test it thoroughly and then abandon > the whole thing after a couple of months, or do I *have* to maintain the > class forever and ever? : ) > > Thanks - > Jonas Koch Bentzen > > > -- > PEAR Development Mailing List (http://pear.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php