[OPENJPA-1983] Merge of lazily fetched fields, and merge of managed entities deviates from spec

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.1.0, 2.2.0
• Fix Version/s: 2.0.2, 2.1.2, 2.2.0
• Component/s: jdbc
• Assignee: Richard G. Curtis
• Reporter: Pradyumna Achar
• Created: 19/Apr/11 19:51
• Updated: 21/Sep/16 14:38
• Resolved: 28/Oct/13 21:21

Description

Attached is a test case that illustrates this fail (You can place it into openjpa-persistence-jdbc/src/test/java/org.apache.openjpa.persistence.merge)

Problem 1: Section 3.2.7.1 (Merging Detached Entity State) of the specification says that "The persistence provider must not merge fields marked LAZY that have not been fetched: it must ignore such fields when merging.". The attached test case illustrates that OpenJPA 2.1.0 does not ignore fields marked LAZY that have not been fetched.
Problem 2: In the same section, the specification says "If X is a managed entity, it is ignored by the merge operation...". But OpenJPA 2.1.0 doesn't seem to ignore them.

Issue Links

• is cloned by: OPENJPA-2408 CLONE - Merge of lazily fetched fields, and merge of managed entities deviates from spec
• is depended upon by: OPENJPA-2540 merge without DetachedStateField deletes lazy fields in embedded entities