Integrity on large sites

Поиск
Список
Период
Сортировка
От Naz Gassiep
Тема Integrity on large sites
Дата
Msg-id 4653A324.1030005@mira.net
обсуждение исходный текст
Ответы Re: Integrity on large sites  ("Stuart Cooper" <stuart.cooper@gmail.com>)
Re: Integrity on large sites  ("Richard P. Welty" <rwelty@averillpark.net>)
Re: Integrity on large sites  (Ron Johnson <ron.l.johnson@cox.net>)
Re: Integrity on large sites  (Ben <bench@silentmedia.com>)
Re: Integrity on large sites  (Scott Ribe <scott_ribe@killerbytes.com>)
Re: Integrity on large sites  (Scott Marlowe <smarlowe@g2switchworks.com>)
Re: Integrity on large sites  ("Alexander Staubo" <alex@purefiction.net>)
Re: Integrity on large sites  (Andrew Sullivan <ajs@crankycanuck.ca>)
Список pgsql-general
I'm working in a project at the moment that is using MySQL, and people
keep making assertions like this one:

"*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."

This sounds to me like MySQLish. A large DB working with no RI would
give me nightmares. Is it really true that large sites turn RI off to
improve performance, or is that just a MySQL thing where it gets turned
off just because MySQL allows you to turn it off and improve
performance? Can you even turn RI off in PostgreSQL? Does Oracle, DB2 or
MSSQL allow you to turn it off? Am I just being naive in thinking that
everyone runs their DBs with RI in production?

- Naz

В списке pgsql-general по дате отправления:

Предыдущее
От: Rick Schumeyer
Дата:
Сообщение: Using a trigger with an object-relational manager
Следующее
От: "Stuart Cooper"
Дата:
Сообщение: Re: Integrity on large sites