Re: CMS, foreign keys, and the legacy of MySQL - Mailing list pgsql-advocacy

From Josh Berkus
Subject Re: CMS, foreign keys, and the legacy of MySQL
Date
Msg-id 4D825A1B.6010805@agliodbs.com
Whole thread Raw
In response to CMS, foreign keys, and the legacy of MySQL  (jj ff <m9mq@live.com>)
Responses Re: CMS, foreign keys, and the legacy of MySQL
List pgsql-advocacy
On 3/17/11 11:52 AM, jj ff wrote:
> Here's a comment I found while googling around on these issues:  "The
> problem isn't that InnoDB itself is slow, it's that enforcing foreign
> key relations is slow. I'm a big fan of referential integrity, but in a
> CMS it's place is in the application layer, not the data layer."  Why
> would anyone say that?  What's the point of using a DB if you're not
> doing to put FKs in it?

Well, they're right ... for InnoDB.  If you're only experience with a
relational database is MySQL, then you're liable to think that FKs are a
disaster.

--
                                  -- Josh Berkus
                                     PostgreSQL Experts Inc.
                                     http://www.pgexperts.com

pgsql-advocacy by date:

Previous
From: jj ff
Date:
Subject: CMS, foreign keys, and the legacy of MySQL
Next
From: damien clochard
Date:
Subject: Re: Proposal for a PostgreSQL Print Magazine