 | |
#1
 
| |||
| |||
|
Removing foreign key constraints -
07-07-2004
, 01:14 PM
#2
| |||
| |||
|
|
Hi there, Wanted to get a feel for what the feeling was out there about removing foreign key constraints on the database side for the n-tier application that enforces the integrity in the middle tier. Theoretically, if the only way the database is updated is through the application there might not be a need to enforce foreign key constraints. Any thoughts? Bob |
If your customer's administrator has interactive SQL
access to the database (which they legitimately
have a right to do as administrators) they will also
be able to inadvertantly screw up the integrity
unless you enforce it with the database.
The probability that this will happen approaches 1.
NPL
--
"It is impossible to make anything foolproof
because fools are so ingenious"
- A. Bloch
#3
| |||
| |||
|
|
Hi there, Wanted to get a feel for what the feeling was out there about removing foreign key constraints on the database side for the n-tier application that enforces the integrity in the middle tier. Theoretically, if the only way the database is updated is through the application there might not be a need to enforce foreign key constraints. Any thoughts? Bob |
1. Whose butt is on the line if the data gets screwed up?
2. Do you subscribe to the theory that the liklihood of an event is
inversely proportional to the desireability of its happening?
3. Is it your boss' idea to do away with FK constraints?
4. Will doing away with FK constraints solve a problem?
#4
| |||
| |||
|
|
Bob wrote: Hi there, Wanted to get a feel for what the feeling was out there about removing foreign key constraints on the database side for the n-tier application that enforces the integrity in the middle tier. Theoretically, if the only way the database is updated is through the application there might not be a need to enforce foreign key constraints. Any thoughts? Bob Go lie down until the feeling goes away! ::grin:: If your customer's administrator has interactive SQL access to the database (which they legitimately have a right to do as administrators) they will also be able to inadvertantly screw up the integrity unless you enforce it with the database. The probability that this will happen approaches 1. NPL If anything, Nick is an optimist. Don't do it. |
#5
| |||
| |||
|
|
Bob wrote: Wanted to get a feel for what the feeling was out there about removing foreign key constraints on the database side for the n-tier application that enforces the integrity in the middle tier. Theoretically, if the only way the database is updated is through the application there might not be a need to enforce foreign key constraints. Any thoughts? |
updated when the rules change, means how many chances to get it wrong?
Quote:
|
Go lie down until the feeling goes away! ::grin:: If your customer's administrator has interactive SQL access to the database (which they legitimately have a right to do as administrators) they will also be able to inadvertantly screw up the integrity unless you enforce it with the database. The probability that this will happen approaches 1. |
would happen.
Sincerely,
Gene Wirchenko
Computerese Irregular Verb Conjugation:
I have preferences.
You have biases.
He/She has prejudices.
#6
| |||
| |||
|
|
Hi there, Wanted to get a feel for what the feeling was out there about removing foreign key constraints on the database side for the n-tier application that enforces the integrity in the middle tier. Theoretically, if the only way the database is updated is through the application there might not be a need to enforce foreign key constraints. Any thoughts? Bob |
of the same topic (in an Oracle-specific context, but applicable
anywhere) interesting:
http://asktom.oracle.com/pls/ask/f?p...:6091237036109
 |
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.