That might be a better approach than what I have now. I'll think
about this. Thank you for the suggestion!
Ian
On May 14, 2008, at 3:17 AM, Leslie P. Polzer wrote:
Also, cached slots are not currently thread safe. If you don't
guarantee that only one thread at a time is working on a par
> Also, cached slots are not currently thread safe. If you don't
> guarantee that only one thread at a time is working on a particular
> object, you can get problems. These slot values are not isolated by
> the transaction mechanism. I'm not sure we should solve that; the
> protection for cache
On May 12, 2008, at 10:23 AM, Leslie P. Polzer wrote:
- Currently cached slots are not rolled back to their initial value
if
transaction aborts. I can add a facility to push the cached value on
the initial read into a per-transaction list that can be used to
reset
the cached slots on an
> - Currently cached slots are not rolled back to their initial value if
> transaction aborts. I can add a facility to push the cached value on
> the initial read into a per-transaction list that can be used to reset
> the cached slots on an abort.
Would it be possible to automatically restore t
Cached slots:
-
- Currently cached slots are not rolled back to their initial value if
transaction aborts. I can add a facility to push the cached value on
the initial read into a per-transaction list that can be used to reset
the cached slots on an abort. Should this be by d
