Re: Duplicate Key / tuning

boothm@ibm.net wrote:
> 
 I've become a fan of the non-keyed physical.  A lot of
> problems go away.
> 
---
I've always been a fan too, but since we started using a lot of
referential constraints, the problems have come back.  When I add a
referential constraint, the system builds a unique key constraint over
the physical and from then on it behaves as a keyed physical.

What's even worse, when I add a referential constraint involving a
physical that was keyed, it creates a unique key constraint that shares
the path already established by the keyed physical. Sound good so far,
right?  But then, when you remove the constraint, it removes the access
path, even though it was only sharing it with the physical and didn't
own it outright!  Then the physical won't work because it can't find
it's access path.

Am I doing something wrong here, or is this a "feature" ??
-- 
Nelson Smith
"Standards are Wonderful....cause there's so many to choose from!"
ncsmith@gate.net
+---
| 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
+---