Quoth Steve Wainstead:
> On Wed, 18 Jul 2001, Joel Uckelman wrote:
>
> > When I added the code for page versioning, I broke support for everything
> > except MySQL, so now I'm trying to bring the other db formats up to speed.
> > Perhaps the changes I just committed in lib/pgsql.php and
>
> Oh, don't worry. We are going to switch to a generic DBMS interface --
> either PEAR's DB or the dbx functions -- quite soon. Perhaps even tonight
> if I stay in and hack. I have done some rudimentary testing with the dbx
> stuff and it works fine. DB is a much larger hoop to jump through.
>
> We will gain two big things: only one database interface to support, and
> multiple databases will now be supported. I'm leaning towards PEAR/DB at
> the moment since it's more developed, supports more databases and PEAR
> looks like the way to go right now.
Before looking at the Pear DB and dbx docs, I was hoping one of them would
handle all of the db formats we use now; alas, they only support *SQL. That
aside, using one of these would reduce the number of separate db libs we
have to maintain, which is a Good Thing. I see that we'd gain support for
seven extra SQL servers (!) if we went with Pear DB, as opposed to gaining
two and losing msql with dbx. I'm not sure how much demand there is for
Phpwiki to work with any of those, however, and even so, the dbx docs read
as though support for more DBs is forthcoming. And while Pear DB seems more
featureful than dbx, lots of those features are ones I don't see us using.
So my vote is for dbx, though if you make it work with Pear DB, I won't
change it back. ;)
Anyway, I still need to update the dba, dbm, and flatfile libs, since
neither Pear DB nor dbx handles those at present.
--
J.
|
