Loading...

XML

Word

Printable

Type: Bug
Resolution: Won't Do
Priority: Major
Fix Version/s: TBD EAP 5
Affects Version/s: EAP 5.0.0.CR1, EAP 5.0.0.BETA, EAP 5.0.0.CR2, EAP 5.0.0.CR3, EAP 5.0.0.CR4 (FCS and BETA2), EAP 5.0.0.CR5, EAP 5.0.0
Component/s: Hibernate
Labels:
None

Workaround:

Workaround Exists
Workaround Description:

Hide

Leave ORDER_INSERTS at the default value of FALSE when Embedded classes are used.

or

Explicitly call session.save() on child objects to enforce their SQL insertion orders.

Show
Leave ORDER_INSERTS at the default value of FALSE when Embedded classes are used. or Explicitly call session.save() on child objects to enforce their SQL insertion orders.
Release Note Text:

Hide
When batch insert statements are ordered, embedded classes are not taken into account. There are two possible workarounds for this issue. The first is to set <varname>ORDER_INSERTS</varname> to <literal>FALSE</literal> when embedded classes are used. The second option is to explicitly call <literal>session.save()</literal> on child objects to enforce their SQL insertion orders.

Show
When batch insert statements are ordered, embedded classes are not taken into account. There are two possible workarounds for this issue. The first is to set <varname>ORDER_INSERTS</varname> to <literal>FALSE</literal> when embedded classes are used. The second option is to explicitly call <literal>session.save()</literal> on child objects to enforce their SQL insertion orders.
Release Note Status:
Documented as Known Issue

clones

JBPAPP-5554 Document - CLONE -Backport HHH-3683 - Embedded classes not taken into account when order_inserts is enabled