Issue Details (XML | Word | Printable)

Key: NUCCORE-817
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Unassigned
Reporter: Andy Jefferson
Votes: 0
Watchers: 0
Operations

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

Non-referential flush should mark ObjectProvider as flushedNew after insert

Created: 09/Mar/12 07:36 PM   Updated: 30/Mar/12 09:25 AM   Resolved: 09/Mar/12 07:36 PM
Component/s: Code Structure, Persistence
Affects Version/s: 3.0.9
Fix Version/s: 3.0.10, 3.1.0.m1


 Description  « Hide
Some of JDOStateManager.internalMakePersistent was not copied across when writing the non-referential flush process, so we need this step adding

Sort Order: Ascending order - Click to sort in descending order
Andy Jefferson added a comment - 09/Mar/12 07:36 PM
SVN trunk and branches/3.0 have this

Chris Rued added a comment - 10/Mar/12 07:09 AM
I just want to confirm that after updating to the svn trunk (and getting this fix), the Exception I reported in NUCMONGODB-63 no longer occurs.

Thanks for the very fast response.