[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [eclipselink-dev] Fixed Bug 362913 - Aggregate mappings do not support "isNullAllowed' when aggregate has OneToOneMapping relationships
|
Correction to the patch
In AggregateObjectMapping don't need to do anything if isNullAllowed is
false.
In DDLGenerationJUnitTestSuite.testEmbeddedOneToOne made sure that
correct table name is used by custom sql on all database platforms.
Checked the correction patch into both 2.4 and 2.3.3
On 2/24/2012 4:34 PM, Andrei Ilitchev wrote:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=362913
AggregateObjectMapping allows null if it has ForeignKey OneToOneMapping.
All CollectionMappings as well as ObjectReferenceMappings (such as
OneToOne) that use target foreign key still disallow null (mow the
warning is logged when that happens).
Test: DDLGenerationJUnitTestSuite.testEmbeddedOneToOne
Checked the patch into both 2.4 and 2.3.3
Reviewed by Tom.
Thanks,
Andrei
_______________________________________________
eclipselink-dev mailing list
eclipselink-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipselink-dev
