PostgreSQL vs MySql Nov 29 2005

So at the minute I’m using PostgreSQL for most apps I write that require a database back-end, including this very blog. It’s stable, it’s reliable, and it’s easy to use under .Net/Mono. However, I have recently been playing around with v5 of MySql. It had been awhile since I last toyed with MySql, and back then it’s lack of stored procedures was a bit of a pain in the ass. Now though, MySql really seems to be a lot more professional, and a lot more comprehensive, while still being lightning quick as always. I am quite tempted to start using that over PostgreSQL again and see how I get on. In fact, thanks to the xFramework database library (xFramework.Common.Db), changing databases will be as easy as writing a new database provider that implements IDbProvider, setting up the database schema on the new db server, migrating over any existing data between the two databases, and re-configuring the affected apps to use the new IDbProvider. I think xFramework could do with a MySql data provider anyhoo ;-)