Re: [eclipselink-dev] Bug 249037: JPA 2.0 persisting list item index

["Andrei Ilitchev" <andrei.ilitchev@xxxxxxxxxx>]

Checked into tunk.

Correction - set order to null after object removed from list

Added test to verify that order field is set to null after object removed from
list.
Also fixed handling of nulls in
DirectCollectionMapping.valueFromRowInternalWithJoin: the fix I previously put
in there (see bug 278126) caused creation of collections with a sole member
null - when an empty collection was expected.

----- Original Message -----

From: Andrei Ilitchev

To: Dev mailing list for Eclipse Persistence Services

Sent: Friday, June 19, 2009 12:30 PM

Subject: [eclipselink-dev] Bug 249037: JPA 2.0 persisting list item index

https://bugs.eclipse.org/bugs/show_bug.cgi?id=249037

Checked into trunk:

 

JPA - added CorrectionType annotation and processing

Tests:
InheritedModelJunitTest.testBreakOrder_CorrectionType_EXCEPTION;
InheritedModelJunitTest.testBreakOrder_CorrectionType_READ_WRITE

Tried to change the name of ORDER_COLUMN in inheriting class
(NoviceBeerConsumer) using @AssociationOverride, but it didn't work: the
orderListField set in the mapping in NBC remained the same as in
MappedSuperclass. For now using the same order column name for both NBC and
EBC.

Code review bu Guy is pending.

Thanks,

 

Andrei

 

---

_______________________________________________
eclipselink-dev mailing list
eclipselink-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipselink-dev