My Oracle Support Banner

RDBPROD: FETCH/FIND NEXT WITHIN <CALC-set> May Not Search Entire Set (Doc ID 63065.1)

Last updated on NOVEMBER 19, 2019

Applies to:

Oracle CODASYL DBMS - Version 4.0a and later
HP OpenVMS VAX
HP OpenVMS Itanium
HP OpenVMS Alpha

Purpose

In the "Database Design Guide" (Feb 1994) for DBMS it states on page 4-16:

Do not use CALC mode when the application needs to look at all or most of the data in a relationship.

Further, on page 4-17 it states:

Because CALC sets are designed for single-record lookup, it is illogical to perform a FIND NEXT or FIND PRIOR in a CALC set. However, if duplicate keys exist, performing a FIND NEXT or FIND PRIOR is the only way to retrieve those duplicate records.

It does not explain why FIND NEXT or FIND PRIOR is illogical. 

Scope

CODASYL DBMS programmers

Details

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.