#23 Porting to PostgreSQL

[Robby Russell]

This evening, I began porting pmtool to PostgreSQL.

I currently have the schema working (could be tuned up
a bit) but for the time being it works.

I've been able to create a db.pgsql.inc.php file and
began modifying the code.

So far, there have only been a few issues here and
there that I am addressing. I would like to build a
port that is A. compatible with the mysql version and
B. perhaps move it to PEAR.

A few issues I found right away were, the table 'user'
is a keyword in postgresql, so you can change it to
users and update the config.inc.php file to change the
table name for users.

The other is the use of the mysql function password().
I can either A. get rid of this usage or B. create a
pgsql function that performs the same function
(assuming its just md5 or something?)

Email me at robby@planetargon if you'd like to help out
and such..and/or maybe the project manager will bring
me on board and I can work with the team members..in
either case... I'm 20% working right now in pgsql. :-)

[Anonymous]

Logged In: YES
user_id=223719

I recently began porting PMTool to Oracle via PEAR DB. I am still
working out some minor issues, but it should be complete very soon. I
would also say that the table definitions could be tuned up, but it works
rather well so far. I had to rename the class in db.inc.php to pmt_db so
that it did not conflict with PEAR DB. I also had to change some table
definitions because some column names conflicted with Oracle, so my
naming convention for tables is tablename_columnname. Most of the
issues that I am resolving are related to those changes. Please let me
know if you are interested in my patches. FLINN _AT_ ACTIVEINTRA
_DOT_ NET