Re: CMS, foreign keys, and the legacy of MySQL

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: jj ff <m9mq(at)live(dot)com>
Cc: pgsql-advocacy(at)postgresql(dot)org
Subject: Re: CMS, foreign keys, and the legacy of MySQL
Date: 2011-03-17 18:59:39
Message-ID: 4D825A1B.6010805@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-advocacy by date

  From Date Subject
Next Message damien clochard 2011-03-17 20:20:46 Re: Proposal for a PostgreSQL Print Magazine
Previous Message jj ff 2011-03-17 18:52:33 CMS, foreign keys, and the legacy of MySQL