Issue Details (XML | Word | Printable)

Key: NUCCORE-1034
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Minor Minor
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

DetachAllOnCommit for class that is not detachable can cause "Object is managed by different ObjectProvider"

Created: 24/Apr/13 11:42 AM   Updated: 15/May/13 09:31 AM   Resolved: 24/Apr/13 11:42 AM
Component/s: Persistence
Affects Version/s: 2.2.4, 3.0.11, 3.1.4, 3.2.2
Fix Version/s: 3.2.3


 Description  « Hide
If we have classes that are not detachable, when they are detached they migrate to transient as per the JDO spec. Whilst using detachAllOnCommit this can lead to the object being made transient, and then later on trying to detach it again and giving the message about being managed by a different "Object Manager"

Sort Order: Ascending order - Click to sort in descending order
Andy Jefferson added a comment - 24/Apr/13 11:42 AM
SVN cleans this up now, and fixes the message to not refer to ObjectManager (since that hasn't existed for some time)