| From: | Naz Gassiep <naz(at)mira(dot)net> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Integrity on large sites |
| Date: | 2007-05-23 02:12:52 |
| Message-ID: | 4653A324.1030005@mira.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stuart Cooper | 2007-05-23 02:27:54 | Re: Integrity on large sites |
| Previous Message | Rick Schumeyer | 2007-05-23 01:21:56 | Using a trigger with an object-relational manager |