Current status:
The PearDB branch in CVS uses Pear::DB for the database connection. It's
tested and works with MySQL as the back-end database. More testing is
necessary for other back-end databases, like PostgreSQL.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Finally, the code in the PearDB branch works on both MySQL and PostgreSQL.
I've replaced all instances of the reserved SQL-word 'user' in the database
schema and PHP files. In a couple files the SQL is implemented differently for
PostgreSQL than for MySQL, due to differences in the vendor specific SQL
dialects.
What remains is more testing on both database backends, to squash the
remaining bugs (if any).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=1253109
Current status:
The PearDB branch in CVS uses Pear::DB for the database connection. It's
tested and works with MySQL as the back-end database. More testing is
necessary for other back-end databases, like PostgreSQL.
Logged In: YES
user_id=1253109
Finally, the code in the PearDB branch works on both MySQL and PostgreSQL.
I've replaced all instances of the reserved SQL-word 'user' in the database
schema and PHP files. In a couple files the SQL is implemented differently for
PostgreSQL than for MySQL, due to differences in the vendor specific SQL
dialects.
What remains is more testing on both database backends, to squash the
remaining bugs (if any).