At 06:17 PM 10/15/97 -0400, you wrote:
>Therein lies the problem. A SQL view does NOT have an access path. Take a 
>look. Try creating a view over a million record table, its size will be < 
>20K. Unless IBM is real good at access path compression there is no access 
>path under the view.

>>I think that a view _is_, in fact, the same as a static select/omit access
>>path, sans ordering, since it is a logical file, whose access path will be
>>maintained as any other logical file. Couldn't the implementation, then, be
>>SELECT * FROM view ORDER BY fieldlist, where the ORDER BY matches the index
>>(or some other keyed logical file)? I don't know what the SQL engine will
>>do under the covers.

Ahhh! So is the view maybe an access _plan_, along the lines of what is
used with embedded SQL? I'm going to try creating a view and then using a
SELECT over it with DEBUG on, so I can see what it's doing. Will report back.

Vernon Hamberg
Systems Software Programmer
Old Republic National Title Insurance Company
400 Second Avenue South
Minneapolis, MN 55401
(612) 371-1111 x480

| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MAJORDOMO@midrange.com
|    and specify 'unsubscribe MIDRANGE-L' in the body of your message.
| Questions should be directed to the list owner/operator: david@midrange.com

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-2022 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.