Issue Details (XML | Word | Printable)

Key: NUCCORE-778
Type: Bug Bug
Status: Open Open
Priority: Major Major
Assignee: Unassigned
Reporter: Marius Heinzmann
Votes: 0
Watchers: 0

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

Lazily created persistent Set in jdoPreStore results in wrong object persistence order

Created: 04/Nov/11 05:02 PM   Updated: 04/Nov/11 05:04 PM
Component/s: Persistence
Affects Version/s: 3.0.2
Fix Version/s: None

File Attachments: 1. GZip Archive datanucleus_test.tar.gz (14 kB)

Environment: DS is backend by Mysql

 Description  « Hide
When instantiating a previously nulled Set in the jdoPreStore method, then DN persists the added objects before the parent object is persisted to the DB. Therefore the parent foreign key constraint in the join table of the set will fail.

Marius Heinzmann added a comment - 04/Nov/11 05:04 PM
The test case reproducing the described issue.

Also note: The failed addition of an element to the set is only logged as an error and the exception is not propagated as it IMHO should be.

Marius Heinzmann made changes - 04/Nov/11 05:04 PM
Field Original Value New Value
Attachment datanucleus_test.tar.gz [ 11522 ]