Well, repositioning file pointer, for instance, to get another record from the PF/table.

Dealing with a PF with 100.00 records are more have impact on performance, IIRC.

SQL is not the haarlemmerolie in some cases.

Regards,
Carel Teijgeler

Op 15-9-2017 om 14:48 schreef D*B:
<Carel>
In the original example there was also reading previous and next, which means using a cursor in SQL.
What is the performance impact of opening and closing a cursor compared to the traditional RLA approach?
</Carel>

why open and close a cursor? first read after positioning needs an open (for next and previous 2), then read prev or next is reading from an ODP as it is for RLA. And again in real world programms I/O performance is more than comparing microseconds for programms doing nothing.

D*B


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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.