|
> If you do NOT put them on the physical you cannot add a referential > constraint to this physical to another physical. For example if I have a > PF called CUSTMAST and a logical with CUSTMASTL1 and the unique key is > only in CUSTMASTL1 then I cannot do a ADDPFCST on my order file to make > sure that the customer number is on file. A (Parent) PF does not have to have a unique key defined to establish a Referential Constraint. If no key exists, the ADDPFCST comand will define the Parent Key as a Primary Key automatically - i.e. adding a Key Constraint to CUSTMAST. Of course, it might be preferable to define a Unique or Primary Key Constraint beforehand using ADDPFCST (or SQL). DDS or SQL (Index) definitions do not directly influence the Primary/Unique Key Constraint. Brian Parkins
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.