Issue Details (XML | Word | Printable)

Key: NUCRDBMS-399
Type: Bug Bug
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 Store RDBMS

Insert of 1-N bidir relation with element having CLOB, on Oracle, fails to set the CLOB in some elements

Created: 24/May/10 11:09 AM   Updated: 11/Jun/10 01:38 PM   Resolved: 24/May/10 11:35 AM
Component/s: ORM, Types
Affects Version/s: 2.0.0.release, 2.0.1, 2.0.2, 2.0.3, 2.0.4, 2.1.0.m1, 2.1.0.m2, 2.1.0.m3
Fix Version/s: 2.0.5, 2.1.0.release


 Description  « Hide
If we have a class Owner with a List of Element (which have a CLOB field) in a bidir relation, and we try to persist a List of 2 elements by calling pm.makePersistent() on the first element, this fails to set the CLOB on one element.

The MappingCallbacks.postInsert isn't being called in time and the List comes in with a refresh which nulls out the CLOB value.

Sort Order: Ascending order - Click to sort in descending order
Andy Jefferson added a comment - 24/May/10 11:35 AM
Added MappingCallbacks.insertPostProcessing step for Oracle handlers

Andy Jefferson added a comment - 27/May/10 08:13 AM
Also applied to 2.0 branch