Project

General

Profile

bug #7357

Clone methods correctly implemented for bidirectional relationships

Added by Andreas Müller about 1 year ago. Updated about 1 year ago.

Status:
New
Priority:
New
Assignee:
Category:
cdmlib
Target version:
Start date:
04/20/2018
Due date:
% Done:

0%

Severity:
normal
Found in Version:

Description

Many clone methods do not take into account that links to single objects or collection items require handling of bidirectionality during cloning, otherwise the other object does not know about the new clone, but should (in many cases).

See Revision d014205f as an example.

Associated revisions

Revision d014205f (diff)
Added by Andreas Müller about 1 year ago

ref #7357 implement clone correctly for TypeDesignationBase

Revision 54d2eeaf (diff)
Added by Andreas Müller about 1 year ago

ref #7357 fix TaxonName.clone test in model

Revision f3e2aa7a (diff)
Added by Andreas Müller about 1 year ago

#7357 fix failing converter test in service layer after fixing typeDesignation.clone

Revision 2c84f57a (diff)
Added by Andreas Kohlbecker about 1 year ago

ref #7357 removing workaround for incomplete DerivedUnit.cone() in DerivedUnitConverter

Revision 3359fa6d (diff)
Added by Andreas Müller about 1 year ago

ref #7357 fix test for CategorialData.clone and move it from DescriptionElementTest to CategoricalDataTest

Revision c6eb0a3c (diff)
Added by Andreas Müller about 1 year ago

ref #7357 fix clone for quantitativeData and StatisticalMeasurementValue

History

#1 Updated by Andreas Müller about 1 year ago

  • Description updated (diff)

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 40 MB)