In order for this site to work correctly, and for us to improve the site, we need to store a small file (called a cookie) on your computer.
By continuing to use this website, you agree to our cookies and privacy policy.
  
Home page Home page Home page Home page
Pixel
Pixel Header R1 C1 Pixel
Pixel Header R2 C1 Pixel
Pixel Header R3 C1 Pixel
Pixel

@ATTACK - @List.Active

Variable set by the system to indicate the status of the pending select list (if applicable). 0 means that there is not currently a select list active, 1 means that the select list is latent and 3 means that the select list resolved.

The question has been raised "Why is a BTREE.EXTRACT so fast, but a LIST WITH so slow - even when it uses indexes?". The answer lies in case sensitivity. As the user might want a specific case match in an index lookup in LIST (and indexes are generally case insensitive), the system calls BTREE.EXTRACT for the key list, and REDUCE then reads each record in turn to see if the contents match exactly (including case) what the user requested. The finished resolved list is presented to the LIST processor. The keyword NORESOLVE in the list statement would instruct REDUCE to do this check as the LIST statement progressed thus improving speed. Can be amended.

(Volume 2, Issue 3, Page 11)
Pixel
Pixel Footer R1 C1 Pixel
Pixel
Pixel
Pixel