At 10:06 AM 20/11/2003 +0200, you wrote:

>Hi All,
>
>I have the following case:
>
>1. TBL_PARTY, primary key PARTY_ID
>2. TBL_PERSON references TBL_PARTY on PARTY_ID
>
>So, PARTY_ID is a FK in TL_PERSON which means I have an index created,
>but PARTY_ID is a PK also. I don't like tables without PK defined, but
>in that case I will get 2 indexes on one and the same field which is
>not good also.
>
>What is your opinion about that? Can I avoid one of the indexes?

It's a 1:1 relationship, so it's very easy to implement a cascading delete
(if wanted) and existence rules using custom triggers. Drop the FK
relationship.

heLen