Re: Integrity on large sites

From: Scott Ribe <scott_ribe(at)killerbytes(dot)com>
To: Naz Gassiep <naz(at)mira(dot)net>, <pgsql-general(at)postgresql(dot)org>
Subject: Re: Integrity on large sites
Date: 2007-05-23 16:54:01
Message-ID: C279CDC9.74A2A%scott_ribe@killerbytes.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> "*Really* big sites don't ever have referential integrity. Or if the few
> spots they do (like with financial transactions) it's implemented on the
> application level (via, say, optimistic locking), never the database level."

Pure, utter, unadulterated bullshit. Speaking as someone who had years of
experience with Sybase SQL Server before either MySQL or PostgreSQL were
even created...

Some big sites do of course juggle performance vs in-database run-time
checks, but the statements as typically presented by MySQL partisans, that
it's never done in the database level, is just wrong. Whether it's a direct
deception, iow speaker knows it to be false, or an indirect deception, iow
speaker is implying a level of expertise he does not possess, either way I
would categorize it as a lie.

--
Scott Ribe
scott_ribe(at)killerbytes(dot)com
http://www.killerbytes.com/
(303) 722-0567 voice

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message lest mitsui 2007-05-23 16:55:12 application online upgrade strategy
Previous Message Rick Schumeyer 2007-05-23 16:21:38 Re: Tsearch2: upgrading from postgres 8.1.x to 8.2.x