Cache
Lookup |
result |
None |
No data is cached or retrieved from the cache
for the table. |
NotInTTS |
When s records are selected by a Primary
Key or a unique index, the registry value
is cached when within a
transaction (after ttsBegin).
No cache scans made outside the transaction are used. When inside a
transaction, the record is read once from the database and later from the cache. The record is locked by select when read
in a transaction, which ensures that the
cached record is not updated when the transaction is active. |
Found |
When records are selected by a Primary Key or a
unique index, the record value is cached for the duration of the if they are or
until the record is updated. All "selects" return the cache value if the record exists
there. Um "select for Update"
in a transaction forces the database read and replaces the cached record. |
FoundAndEmpty |
It has the same functionality as Found,except that if "select"does
not return data,the absence of a record is cached.
|
EntireTable |
The entire table is cached on the server as soon
as at least one record is selected from the. |
You can usually set the Lookup Cache of a table according to the relationship below, however there may be exceptions.
Table
Group |
Cache
Lookup |
Miscellaneous* |
Do not use and this Table Group for custom tables. |
Parameter |
EntireTable |
Group |
Found |
Main |
Found |
Transaction, |
NotInTTS |
Framework |
Does not apply |
Reference |
Found |
Worksheet, and WorksheetLine |
NotInTTS |
Hope you find this helpful and will come up with another interesting blog post!
No comments:
Post a Comment