RE: Primary & Foreign key constraints

From: Abdul Aleem <abchaudhary-ho_at_beaconhouse.edu.pk>
Date: Tue, 23 May 2000 11:26:36 +0500
Message-Id: <10505.106324@fatcity.com>

To add to what Deepak has said,

There are no merits to this practice. I would say that the person who designs a database without FK and PK is highly unprofessional (an idiot) and has absolutely no idea of RDBMS design. This can lead to current and future problems.

I would suggest to enforce RI constraints at database level at your earliest.

• Heavy Front-end, (more network traffic, client machines with good specs.)
• Lengthy code, (difficult in locating problems and making modifications)
• If someone gains access to the database without front-end, can insert a lot of garbage without much of a hassle.
• When you hire new developers they will have to follow the same wrong-practice unless someone takes pain and define RI (Referential data Integrity constraints).
• If you try to implement RI, be prepared to get a lot of duplicate records especially in daily transaction tables.

I would appreciate if you could tell what application is that

Hope this helps

Regards,

Aleem

		-----Original Message-----
		From:	Thapliyal, Deepak [mailto:DThapliyal_at_ea.com]
		Sent:	23 May, 2000 11:16 AM
		To:	Multiple recipients of list ORACLE-L
		Subject:	RE: Primary & Foreign key constraints

		Rufus,

		if you try to enforce RI at the app level .. u are looking
in the face of
		increased IO hits as you try to manually force RI rules..
may also lead to
		funny situations (mutating/constraining) as you start
playing with triggers
		trying to accomplish the same. thats all my brain cells
allow me to write at
		this point :-((

		deepAk

		-----Original Message-----
		Sent: Monday, May 22, 2000 10:44 PM
		To: Multiple recipients of list ORACLE-L


		Hi Guru's,

		Will any one tell, if there is any specific advantage if we
don't have
		primary & foreign key constraints at database level. In one
of our major
		applications I have seen, they do not  have primary &
foreign key
		constraints defined at database level, but handled at the
front end level.
		Can anyone tell what could be the merits if any ? 

		TIA,
		Rufus.
		-- 
		Author: Rufus Chinnam
		  INET: rufus.chinnam_at_emirates.com

		Fat City Network Services    -- (858) 538-5051  FAX: (858)
538-5051
		San Diego, California        -- Public Internet access /

Mailing Lists         

---

                To REMOVE yourself from this mailing list, send an E-Mail message

                to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in

		the message BODY, include a line containing: UNSUB ORACLE-L
		(or the name of mailing list you want to be removed from).
You may
		also send the HELP command for other information (like
subscribing).
		-- 
		Author: Thapliyal, Deepak
		  INET: DThapliyal_at_ea.com

		Fat City Network Services    -- (858) 538-5051  FAX: (858)
538-5051
		San Diego, California        -- Public Internet access /

Mailing Lists         

---

                To REMOVE yourself from this mailing list, send an E-Mail message

                to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in

		the message BODY, include a line containing: UNSUB ORACLE-L
		(or the name of mailing list you want to be removed from).

Received on Tue May 23 2000 - 01:26:36 CDT