[Phpsqliteadmin-devel] proposed class conversion

[Steve D. <sd...@wo...>]

Ok guys,

I've been spouting this dream of mine to use PEAR's native DB class as 
the backend API for connecting to the SQLite database, and here's how I 
think it can be done.

There's two reasons I want to use the DB class though -- one, it's 
installed with almost every php installation and it's very nice class 
(well documented too), and two, I'm already really familiar with it. :)

Anyway, this email is my proposal on ditching the old class, and 
integrating the parts that PEAR's doesnt support into PSA, and how it 
can be done.

http://sdibb.frogcircus.org/psa/psa_class_conversion.html

I put together a quick spreadsheet that has four columns:

SPLSQLite - has the functions of the old class you guys were using, and 
as nice as I think it is, I have no problems about abandoning it since 
DB.php already supports half the functions (as you'll see), and the 
other half can be put into the PSA class.

DB - If there's an entry in the column, then that value can replace that 
function of the old class.  In almost every case it's probably going to 
take a bit of manipulation and code cleanup to use DB instead.

PSA - The new class I already started working on, which will pick up any 
slack that DB can't handle, and at the same time pick up any functions 
that psa is using right now and integrate them in as well.  The PSA 
class of course won't be limited to just that stuff, but that will be 
some if of its main functions.

PHP - The actual php functions that the PSA class would use.

What do you guys think?  I hope my little spreadsheet makes some sense. :)

I can go ahead and start on the class conversion, but I just wanted to 
make sure we're all on the same page, and you guys don't think it's a 
bad idea using PEAR instead or anything.

Steve