From: Kevin Brown <blargity@...>
Date: 2005-12-01T22:14:24+09:00
Subject: Re: Ruby Enterprise App Design Advice

On Thursday 01 December 2005 04:07, Robert Klemme wrote:
> > 3. Database -- MySQL or Postgres - We need transaction support and
> > data integrity -- doubts about MySQL in these areas. We also need
> > good join performance - database is heavily normalized, may
> > denormalize if needed. Separate DBs for things like Logging/Auditing
> > vs. Content. Want to cluster DBs. We want connection pooling.
> > Considering making some modifications to DBI.  Use stored procedures
> > in the database, no sql in the code/dynamic sql. I loathe O/R mappers
> > for complex databases and they would likely bring our system to a
> > screeching halt. Unfortunately we cannot afford to use Oracle right
> > now.
>
> I don't have experience with postgres and mysql.  Given the fact that
> mysql is quite new and so are stored procedures and the way it deals with
> transactions I'd probably tend to use postgres.

You could write a whole book here, but from what you say I'd go with Postgres.  
If you want to search through the MySQL support forums you'll find a lot more 
complaints about corrupt dbs, etc.  Postgres favors reliability over speed 
and ease of use.  Not that it's slow at all, just that that was their first 
concern.  I almost always use Postgres now just because it's so nice to work 
with (in my opinion of course). :-)