rob wrote:
Let's keep it simple then. What sound business reason is there to not have a primary key constraint on the item master file?

...especially when it can be easily added (created) with a ADDPFCST command even if there is no key in the DDS.

I have a need from time to time to update a couple particular old databases with a group of records that are supplied to me. The PFs have no keys. The new records can be either updates of existing records or additions of new records to the files. There are a number of potential physical files to be updated, all of them with very different formats.

The simplest way for me to do it in _this_ case is to:

1. ADDPFCST to add a primary key.
2. CPYF using *UPDADD
3. RMVPFCST to drop the key that I added. (I'd gladly leave it in, but there are some secondary issues.)

The only point is that it's such an easy process to add a primary key that it's essentially trivial. It's almost as easy to remove the constraint later.

Tom Liotta

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by 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].