RE: Primary & Foreign key constraints

From: Abdul Aleem <abchaudhary-ho_at_beaconhouse.edu.pk>
Date: Wed, 24 May 2000 10:51:22 +0500
Message-Id: <10507.106485@fatcity.com>

I am really really sorry for my words, I will be careful next time.

The reason I wrote so strongly about it was my first practical experience when I had to do the same. Unable to correct the data in time, I had to introduce a temporary column to enforce RI. It took months to finalize data.

Hope my apology will be accepted.

Regards,
Aleem                 

                Well, well, well...

                Hi there from a highly unprofessional idiot... :P

                Perhaps you would like to tell me why I should enforce RI at the database on all cases?

                But before you start, go design, build and implement an Oracle data warehoue or data mart.

		In general,
		I use RI at the database it to ensure that the data rules
are consistent.
		I use RI at the app is to ensure the application specific
rules are consistent.
		And these are not necessarily the same thing.

		The data loaded into a data warehouse already conforms to

both data and application rules before it's stored.

                Personally, to mis-quote you with a few changes,

                "There are no merits to this practice. I would say that the person who

                BUILDS a database WITH FK and PK REGARDLESS is highly unprofessional

                (an idiot) and has absolutely no idea of RDBMS IMPLEMENTATION. This can lead to

                current and future problems. " Received on Wed May 24 2000 - 00:51:22 CDT