| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Mailing Lists -> Oracle-L -> RE : RE: Primary & Foreign key constraints
As a fine example of unprofessional idiots, we can mention the designers
of the Oracle kernel, unless I have missed something in sql.bsq :-).
Joke apart, I fully subscribe to the advice of defining PKs and FKs in general. True, they regularly make even the mildest-mannered DBA swear, and since they are enforced on COMMITs, ergonomy often leads to code redundant checks in applications (such as implicitly checking the existence when fetching the string associated with the code which has just been entered). However, the simple fact of clearly defining PKs and FKs may point to flaws in the database design and have a great virtue : they provide minimum documentation.
Regards,
Stephane Faroult
email: sfaroult_at_oriolecorp.com
Oriole Corporation
Voice: +44 (0) 7050-696-269
Fax: +44 (0) 7050-696-449
Performance Tools & Free Scripts
> 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
Received on Tue May 23 2000 - 04:02:53 CDT
 |
 |