[#EJB-266] Avoid collection loading during cascaded PERSIST (improving performance on heavily cascaded object graphs) - Hibernate JIRA

z - Hibernate Entity Manager

Created: 06/Feb/07 10:33 AM Updated: 11/Jun/08 01:47 PM Resolved: 15/Feb/07 12:08 AM

Return to search

Component/s:

EntityManager

Affects Version/s:

3.2.1

Fix Version/s:

3.3.0.ga

Time Tracking:

Not Specified

File Attachments:	1. persist-test-case.zip (692 kB)
Environment:	hibernate 3.2.2, hibernate-entitymanager 3.2.1.ga

Bug Testcase Reminder (view):
REMINDER: Bug reports should generally be accompanied by a test case
Participants:	Emmanuel Bernard, king and sara forghani

Description

« Hide

hibernate initializes lazy objects traversed by the persist operation;
for example, in this case (the project is attached):

class A has bidirectional one-to-many relationship to classes B1, B2, B3, B4
(b1List, b2List, b3List, b4List)

B1 has bidirectional one-to-many relationship to C1
(c1List)

B2 has bidirectional one-to-many relationship to C2
(c2List)

if we try persisting C2, it will also initialize B1, C1, B4 ... and other existing C2's
(you may find a more complete description of the issue at http://forum.hibernate.org/viewtopic.php?p=2340004#2340004)