DataNucleus JIRA is now in read-only mode. Raise any new issues in GitHub against the plugin that it applies to. DataNucleus JIRA will remain for the foreseeable future but will eventually be discontinued
Issue Details (XML | Word | Printable)

Key: NUCCORE-773
Type: Task Task
Status: Closed Closed
Resolution: Won't Fix
Priority: Trivial Trivial
Assignee: Andy Jefferson
Reporter: Andy Jefferson
Votes: 0
Watchers: 0

If you were logged in you would be able to see more operations.
DataNucleus Core

Only update L1 cache if id not yet present

Created: 27/Oct/11 12:44 PM   Updated: 07/Nov/11 02:57 PM   Resolved: 28/Oct/11 11:12 AM
Component/s: Cache
Affects Version/s: None
Fix Version/s: 3.0.3

 Description  « Hide
Currently we call cache.put() whenever an object needs to be in the L1 cache. Obviously the L1 cache contains the StateManager keyed by the id, and so any field updates are automatically accessible from the L1 cache.

We also have to follow the other key rule that any ObjectManager (PM/EM) will only have a single object for a particular id, and so not updating the L1 cache with some other object will provide a better safeguard.

Sort Order: Ascending order - Click to sort in descending order
Andy Jefferson added a comment - 27/Oct/11 12:55 PM
SVN trunk clears this up

Andy Jefferson added a comment - 28/Oct/11 11:12 AM
JPA TCK had an issue with this idea, and TODO added to investigate it (later)