>>Do you know how R.O. affects SCAN WHILE? I often use a SEEK < parent key>, followed by a SCAN WHILE < still on same parent key >.
>>
>
>There's no R.O. is involved in this case because WHILE clause is not R.O. optimizable.
I see. This sort of confirms my suspicions that this approach (SEEK, followed by SCAN WHILE) would be much faster than a SCAN FOR. (As long as it is not combined with a filter, or with a FOR clause.)
Hilmar.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
