[KLUG Members] PHP and MYSQL

[Adam Williams]

>I'd strongly recommend -not- starting projects off tieing them to a specific DB.  You'll probably get far more done in the long run if you start looking at something like ADOdb for PHP rather than mysql specific calls.
>Besides, then you can port it to PostgreSQL easier later. :)

Or use PHP's unixODBC support.  Then you don't have to depend on the
maintainer of one of the zillion data base abstraction classes to not
having a stroke while walking to get the morning paper.  Push the
abstraction straight of the programming environment (ODBC),  and ODBC
isn't going to "go away" and someone isn't going to rewrite the API
underneath you.

Clearly defined tiers of functionality is a very good long-term
development strategy.

Then you can 'port' it to Oracle later.