Re: referential integrity

ADDPFCST is the animal.  (If one insists on using DDS to describe files. 
Otherwise SQL has a CONSTRAINT keyword that will do it in one statement.)

In your ERD, your customer type file will have a *PRIKEY constrait on 
customer type.
Your Customer master will have a *PRIKEY on customer number and a *REFCST 
on customer type tying it back to your customer type file.
Your order file will have a *PRIKEY on order number and a *REFCST on 
customer number pointing it back to your customer master.
and so on...

Set all these up and iSeries Navigator will draw you a pretty picture.

Other constraints may include check constraints.  Like don't allow 
quantity ordered to be negative.

Rob Berendt
-- 
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





"Dan Bale" <dbale@xxxxxxxxxxxxx> 
Sent by: midrange-l-bounces+rob=dekko.com@xxxxxxxxxxxx
06/30/2004 01:52 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
<midrange-l@xxxxxxxxxxxx>
cc

Fax to

Subject
referential integrity






I started reading up on referential integrity but I've only found
"reference" type of information, i.e. ADDPFCST command description.  The
terminology whizzes way over my head.  I'm sure I have the concepts as I
know exactly where my 20 year old, dusty copy of C.J. Date's Database
treatise is on my bookshelf <g>.

Is there an online "tutorial" article that anyone can recommend?
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.