RE: Implicit Access Path Sharing

Brad,

You are right that it makes no sense unless some other criteria is 
added.  The most likely criteria for me would be to specify that A 
is a unique key.  I would most likely do this when A is the primary key 
to a file and B is a commonly used attribute of the based on file.  This 
allows the commonly used attribute to be retrieved directly from the 
access path without requiring additional I/O.  For example I might set 
up a key of customer number and name and a unique key of customer 
number.  Once this is done, an SQL statement that joins to the customer 
file to select customer names can run significantly faster.

David Morris

>>> "Stone, Brad V (TC)" <bvstone@taylorcorp.com> 04/28/99 07:47AM >>>
Then the question is, if you already had LF1 with A & B as keys (and no
selects, etc), why would you create LF2 with A as a key?  That's redundant
to begin with and does you no good assuming there are no other criteria
needed by either logical.

Bradley V. Stone
Taylor Corporation - OASIS Programmer/Analyst   
bvstone@taylorcorp.com 



+---
| 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
+---