bug #7357
Clone methods correctly implemented for bidirectional relationships
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
ref #7357 implement clone correctly for TypeDesignationBase
ref #7357 fix TaxonName.clone test in model
#7357 fix failing converter test in service layer after fixing typeDesignation.clone
ref #7357 removing workaround for incomplete DerivedUnit.cone() in DerivedUnitConverter
ref #7357 fix test for CategorialData.clone and move it from DescriptionElementTest to CategoricalDataTest
ref #7357 fix clone for quantitativeData and StatisticalMeasurementValue
History
#1 Updated by Andreas Müller over 3 years ago
- Description updated (diff)
