Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
Sepahram
Starting Member
8 Posts |
 Posted - 2001-06-16 : 01:06:23
|
| Dear members,As you know, in MS-SQL (7 and 2000) you can disable enforcing a foreign key constraint in a table. It means you can disable the constraint , insert some rows putting an incorrect FK value which there's no relevant PK for it. Then re-enforce the constraint not for existing data. Microsoft's documents tell us this "facilitates" inserting incomplete data into tables !!! Poof.... It's an obviously violence against Referential Integrity , the second principle of Relational DataBases, isn't it? Does anyone have any explanation for this stupid outrage of RDB rules by a RDBMS? And why shouldn't we use nullable FK in such cases?IMHO, however it downgrade the SQL to the level of "advanced MS-Access". What do you think?Sepahram |
|
|
|
|
|
Referential Integrity Violence [?]