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-528
Type: Task Task
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Andy Jefferson
Reporter: Andy Jefferson
Votes: 0
Watchers: 0
Operations

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

Rationalise the checks on whether to delay datastore ops til flush/commit

Created: 21/May/10 07:24 AM   Updated: 11/Jun/10 01:38 PM   Resolved: 21/May/10 01:48 PM
Component/s: Code Structure
Affects Version/s: None
Fix Version/s: 2.1.0.release


 Description  « Hide
When we have an optimistic txn we delay datastore operations until flush/commit. We also have a persistence property to enable the same thing. SCO classes have one method to check on this, and the ObjectManager has a different method. They should all be rationalised so we can turn this delay on/off as required for complete flexibility

Sort Order: Ascending order - Click to sort in descending order
Andy Jefferson added a comment - 21/May/10 01:48 PM
SVN trunk now bases this around a single method in ObjectManagerImpl, and the user can override the default for optimistic setting using the persistence property.