Rules governing stack purging
JimAultWins at yahoo.com
Mon Oct 30 12:31:10 EST 2006
On 30 Oct 2006, at 16:48, Richard Gaskin wrote:
>> We're in the process of pinning down some anomalies in our system
>> which would seem to suggest that accessing properties can cause a
>> stack to remain in memory such that subsequent accesses are
>> obtained from memory rather than from disk.
>> I would love to be wrong, as it would complicate our system to have
>> to manually purge each stack before accessing it.
To foil the possible caching, you could open another stack that has the same
stack name but different filename, which would replace the first stack.
This would allow you to test for the actual removal of the old data.
/users/me/documents/dataStorage.rev [stack name 'cacheData']
/users/me/documents/dataStorageNull.rev [stack name 'cacheData']
put the cpInventor of stack "/users/me/documents/dataStorage.rev" & " << is
put the cpInventor of stack "/users/me/documents/dataStorageNull.rev" & "
<< is NULL"
Hope this helps get you to your final solution.
More information about the Use-livecode