Re: PF File Definition questions...

Even if you already have a "primary key" logical, when you go to add
constraints, it will require a primary key constraint on the physical.  It
will share the access path of your logical but there is a very important
Gotcha to watch out for.  If you remove all constraints from the physical,
including the primary key constraint, the system will do just that, even
though there was a logical sharing that access path.  You won't get an error
until you try to use your logical again.  For this reason, our utilities
that remove constraints always leave the primary key constraints alone.

-----Original Message-----
From: Dan Bale <dbale@genfast.com>
To: MIDRANGE-L@midrange.com <MIDRANGE-L@midrange.com>
Date: Friday, October 15, 1999 5:15 PM
Subject: Re: PF File Definition questions...


>
>
>Rob,
>
>>> I am trying to follow database rules.  You cannot do
>>> Referential Integrity on files without a primary key.
>
>Could you please enlighten me on this statement?  When you say "primary
key",
>are you implying that a unique keyed access path must be defined in the
physical
>file?  If so, why not in a logical file?  (Which is what I do.)
>
>- Dan Bale
>
>
>
>
>
>+---
>| This is the Midrange System Mailing List!
>| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
>| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
>| To unsubscribe from this list send email to
MIDRANGE-L-UNSUB@midrange.com.
>| Questions should be directed to the list owner/operator:
david@midrange.com
>+---
>

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---