| File Variables |
| Argument passing - Subroutines and Functions - Mike Pope |
| RevTech Replies - Mike Pope (RevTech UK Ltd) |
| Symbol Table Structure |
| SecureUser |
| VERBatim - V25 |
| @ATTACK - @Files.System |
| Advanced Revelation Initialisation Sequence (Overview) by Mike Pope |
| REVMEDIA Revisted |
| @ATTACK - @Cursors(x) |
| @ATTACK - @List.Active |
| @ATTACK - @Rec.Count |
| Playing with Scan Codes |
| QTIPS - SET.MACROS - Choosing Active Macro Set |
| Reader's Forum |
| QTIPS - Btree.Extract |
| Comp |
| Reader's Clinic - Removing "Searching Cross References" Message |
| @ATTACK - @List.Active |
| IConvs / OConvs |
| Reader's Clinic - Stop Lists |
| REVMEDIA Revisited |
| REVMEDIA Revisited |
| QTIPS - Using @Upper.Case and @Lower.Case with Foreign Languages |
| @ATTACK - @Lower.Case |
| @ATTACK - @Upper.Case |
| Sorting out Collation Sequences by Mike Pope |
RevMedia FKB
| Document | V2I3A16 |
| Title | @ATTACK - @List.Active |
| Keywords | @LIST.ACTIVE BTREE.EXTRACT NORESOLVE LIST REDUCE |
| Text | 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) |
Page last modified: 30/01/03