If a unique key constraint is ABSOLUTELY CRITICAL then the only way to be 
absolutely sure is to put the unique key in the PF.

If you want to occasionally remove all access paths from a file to do 
mass-update type functions and add the access paths back, then create LFs with 
the constraints.

There is not a "one better way" - as usual, the answer is, "It depends on what 
you're trying to accomplish."

Michael Polutta
Atlanta, GA

> I have always designed physical files with keys (unique ones).
> Now my eyes have been opened to a world of PF's that have no key that
> are always accessed with keyed logicals. To my surprise, this seems to
> be method of choice for some very common large scale software providers.
>
> I am thinking this matters greatly for future proofing, performance, and
> possible integration with other databases.
>
> My question: Is one way better than the other and what are the reasons?
>
>
> Mark Villa in Charleston SC



As an Amazon Associate we earn from qualifying purchases.

This thread ...


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

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