Ticket #79 (new defect)
Opened 6 months ago
Elephant transaction and cache interactions
| Reported by: | ieslick | Owned by: | ieslick |
|---|---|---|---|
| Priority: | minor | Milestone: | Release 1.0 beta 2 - Testing and Performance |
| Component: | db-bdb | Version: | |
| Keywords: | Cc: |
Description
Potential bug where object instances are cached in memory during a long-running transaction with only read locks (e.g. get-instances-by-value). If the transaction is aborted, the objects are cached in memory. Is this a problem?
Note: See
TracTickets for help on using
tickets.
