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-668
Type: Improvement Improvement
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
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

Allow atomic non-transactional updates

Created: 03/Mar/11 09:39 AM   Updated: 11/May/12 08:28 PM   Resolved: 19/Apr/12 10:43 AM
Component/s: Persistence, Transactions
Affects Version/s: None
Fix Version/s: 3.1.0.m3

 Description  « Hide
When in non-transactional mode, any persist or delete is atomic, in that they happen when invoked. Any update to a field however is not atomic, simply marking the object as dirty and waiting for either the next flush/commit or a close of the ObjectManager to go to the datastore. We should make these updates atomic too, at least as an option

Andy Jefferson made changes - 18/Apr/12 05:43 PM
Field Original Value New Value
Assignee Andy Jefferson [ andy ]
Fix Version/s 3.1.0.m3 [ 11540 ]
Andy Jefferson added a comment - 19/Apr/12 10:43 AM
SVN trunk now adds on nontx atomic updates, adding handling for setXXX on fields of the persistable class, as well as principal mutable SCOs. This is turned off by setting "datanucleus.nontx.atomic" to "false"

Andy Jefferson made changes - 19/Apr/12 10:43 AM
Status Open [ 1 ] Resolved [ 5 ]
Resolution Fixed [ 1 ]
Andy Jefferson made changes - 11/May/12 08:28 PM
Status Resolved [ 5 ] Closed [ 6 ]