Basically I wanna know what people think is better for the eGroupWare suite. I have 3 available to me (MySQL for PHP 4(or 5), MySQLi for PHP5 or PostgreSQL).

Which is faster etc. I estimate over the next few years there will be several thousand records per major table. This will be going in as a production system - so I want to make sure I have the best in place.

Thanks in advance.

Matt.

You'll get as many answers as there's users. My personal preference
is Postgres, always was and will be, for a variety of reasons. It
handles concurrency better (when you said faster: were you looking
for 1 person doing one thing on the database at a time or concurrency?),
it has better compliance with SQL standards and has defined less things
that are unique extensions, and it has sane default settings (e.g. Feb
30 is *not* a valid date).

MySQL folks will argue that MySQL can do clustering and replication
("overlooking" the fact that that only works if the whole DB fits into
RAM which raises a whole lot of other issues [power-/hardware failure?]).

I suggest you go to google and find some articles that "prove" that
MySQL is better, and then some that "prove" that Postgres is better, and
make up your own mind based on what is important in regards to your immediate
requirements of the machine/application.


Cheers,
Tink

I would *always* choose PostgreSQL given the choice. It is much more standards compliant and much more mature than MySQL. Also, MySQL's method of managing users drives me nuts. I cringe whenever I have to deal with it.

Maybe this is a troll, but IMHO MySQL's only reason for existence is the thousands of open source web applications that are tied to it, and people that download it because they think "it's easy", which is due to marketing. Low-end web apps would probably be just as well served with SQLite and higher end web apps would be much better served with PostgreSQL. I honestly can't think of a case where MySQL is technically the best choice!