PHPLIB: Using DB_Sql with MySql and PostgreSQL

Anon

Hello,

Is there a way to have multiple DB_Sql objects connected to differents database ?
The web app I'm working on is using MySql to manage
sessions, authentication and a shopping cart, a PostgreSQL database is used to store everything else.

Thanks for your thoughts.
Regards,
Jeff.

Anon

One DB_Sql object may only work with one database. However, nothing prevents you to create and work with multiple DB_Sql objects simultaneously.

Anon

It's exactly what I'm trying to achieve. PHPLIB defines two differents implementations of the DB_Sql, one per database type:
1/ db_pgsql.inc define a DB_Sql class for PostgreSQL
2/ db_mysql.inc does the same for a MySql database.

Including the two files in the prepend.php3 file fails as we have two differents implementations for the same DB_Sql class.

Do I need to create a super-class of the existing DB_Sql class that can be extended/specialized once for MySql and one for PostgreSQL ?

Thanks for you comments.
Kind Regards,
Jeff.

Anon

Oh, now I see the problem. Hmm.

Yes, I think you are on the right track. Maybe something sort of this (un-validated) code?:

file ext_db_pgsql.inc contains:

<?php
require_once 'db_pgsql.inc';
class OurPG_DB extends DB_Sql
{
var $Host='ourPGSQLhost';
// ...
}
?>

and ext_db_mysql.inc contains:
<?php
require_once 'db_mysql.inc';
class OurMY_DB extends DB_Sql
{
var $Host='ourMYSQLhost';
// ...
}
?>

Hopefully, you should then be able to include both ext_db_pgsql.inc and ext_db_mysql.inc in the same PHP file.

Please give a summary when you find the solution.

Anon

I've just tried and it complains that it cannot redeclare the DB_Sql class...Damned...

Do you now if we can include/require a specific class within a private namespace (ie not the global one), thus prevent class redefinition ?

Rgds,
Jeff.

Anon

It may be time for ugly hacks:
Alter the PHPLIB code so that db_mysql.inc's class is called MYDB_Sql. And alter db_pgsql.inc's class so that it's class is called PGDB_Sql.