Object oriented DB access

So I'm doing a very low scale project - just a simple blog/template for a guy. PHP5/MySQL5 on Apache.

I had programmed mostly the entire thing without abstracting the database, since I figured this project would be pretty specific to my clients needs, now however... I'm really liking how this turned out and would like to use the backend for my own personal site.

The problem is my personal site is on Postgre.

So my question is... do I dick around with PEAR::DB (does that project even exist anymore?) - or, do I just go through searching query by query and changing them by hand?

So lets get this straight.

You have a site on Postgre. You made a new site on MySQL.

First, lets be clear. Both of the RDMSes are shit.

You want to transition from Postgre to MySQL.

While both are shit, it is very clear that Postgre is superior shit to MySQL.

Additionally you want OOP access to the DB, and you want this with PHP.

PHP is not object oriented. It may be able to do some things in an object oriented way, but that does not make it object oriented.

So what you are asking is stupid and misguided. Stop fucking around with this toy shit and step up to the real world of web applications.

You are at the shit tier. You could go mid-shit tier and go with fucking Java and Orcle for fucks sake. Or you could join us up in the God tier and go with .Net and MsSQL sever.

Or if you insist on being a loonix fag you can still .Net on Mono and at a minimum use Postgre for a DB. Then you can run a real IDE like Visual Studio (even on loonix too for free) and stop fucking around with pumped up text editors like Eclipse and that shit. You will also get all the OOP access to your database, even MySQL shit (but don't run that).