Description David Minsky 2010-10-22 12:03:24 EDT

Requirement to partially backport the following bug to the 2.0 line:

Bug 228428 - FORUM: compare non mutable mappings with equals

Situation:

- Create/Read a parent object
- Create a child object with an array of data (e.g. byte[]) mapped with TransformationMapping
- Add child object to parent, begin transaction, persist parent, commit transaction
- Create another object with an array of data (e.g. byte[])
- Change attribute on parent, begin transaction, persist parent, commit transaction
- 2 extraneous update statements are performed for the child object where the child's data has not changed (the array of data)

Problem:

- AbstractTransformationMapping compareForChange does not take into account clone and backup field values may be array data
- Comparison of potential array data needs to be made in order to avoid creating an erroneous change record for array data that has not changed, yet create a correct change record if array data has changed

This change needs to be backported to 2.0. The transaction that made these changes in trunk was created under bug 301599 - https://bugs.eclipse.org/bugs/show_bug.cgi?id=301599 and fixed in r8077 (trunk)