To add to all that has been said the RI constraints
can also help identifying a lot of program DML bugs
!!!! For e.g. A developer maybe trying to insert a
duplicate/orphan record. If there are no RI
constraints it will easily get saved in the DB. This
becomes more relevant when the no of developers and
the size of the application is very high.
- Abdul Aleem <abchaudhary-ho_at_beaconhouse.edu.pk>
wrote: > 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
Do You Yahoo!?
Get your free @yahoo.co.uk address at
http://mail.yahoo.co.uk
or your free @yahoo.ie address at
http://mail.yahoo.ie
Received on Tue May 23 2000 - 10:16:12 CDT
