Comments on: Are foreign keys really necessary in a database design?

By: Tom

Tom — Thu, 22 Dec 2011 21:24:22 +0000

If everybody wrote (and maintained) perfect business logic, there would be no need for foreign keys, but that’s not the case. The main reason for a foreign key is to flag a logic error that would result in an integrity fault, before it leads to a larger mess. In short it’s a debugging capability, a very good and useful crutch. Nothing wrong with that.

By: pranav

pranav — Mon, 04 Jul 2011 16:50:36 +0000

Very nice article and discussion , thanks for comments from Antelio and Mahesh for exploring more about foreign keys.

By: vipin

vipin — Sat, 11 Jun 2011 05:11:28 +0000

INTRODUCTION OF RDBMS…….
DBMS allow you to create and maintain database. In the unit, we will discuss about the various data models and architecture in DBMS. We will discuss RDBMS which is used to store data in the form of related tables. In addtion, we will discuss condidate key, primary key and foriegn key in DBMS.

By: vipin

vipin — Sat, 11 Jun 2011 04:54:49 +0000

CONSTRAINT FOR FOREIGN KEY……………..
>You can add if current feild values are NULL or exist in the referenced table.
>you can delete a FORIEGN KEY constraint.

By: What are common database development mistakes made by application developers? « Thomas van Steenwinckel

Sun, 27 Mar 2011 10:17:37 +0000

[...] Are foreign keys really necessary in a database design? [...]

By: srini

srini — Tue, 23 Mar 2010 11:51:41 +0000

Somebody mentioned Falcon is great, one reason might be this is not having Foreign keys, then how is the data integrity taken care. Is it completely moved to other layers

Johnson can answer this ..

By: Tejaswi

Tejaswi — Fri, 12 Jun 2009 11:56:53 +0000

This is ossem sight
Please sent me difference between Primery & Secondry keys.