Andrew J. Kopciuch wrote: >Just because something is popular, does not mean it is worth while supporting, >nor does it mean it is good. New Kids On The Block anyone? > >
Though the difference between the two RDBMS (okay, so PostgreSQL calls itself an OORDBMS) are many, it is highly unlikely that someone starting out or someone needing to set up a simple app would immediately encounter these differences. That said, I've been following the development of both MySQL and PostgreSQL since 1997 and I decided a few years ago to just use PostgreSQL for, while back then MySQL was said to be faster (which is actually only true for straight INSERTs), PostgreSQL was more feature-ful. I used to write DB programs in C and I haven't had to change any of the apps I've written for Postgres. One of the things I considered was that Postgres developers tend to add the necessary features at the start and go for optimizing their database after while My started out with a simple and fast engine and continues to add more features as time goes by. While there are certainly pros and cons to the two approaches, as a programmer, I like the fact that all the features I need are there and that the engine just keeps getting better rather than to have to go back to my source code whenever a new feature gets incorporated (think sub-SELECTS, COMMIT and ROLLBACK, etc.) -- *Richard Plana, B.Sc., CCNA* Secretary Calgary Linux Users' Group
