Adjusted Create and Read extensions for grass cover erosion outwards failure mechanism - Removed typed Get-function for the hydraulic boundary locations in the persistence registry --> only one type of HydraulicBoundaryLocationEntity exists and thus is typing not necessaryWTI-1657
Adjusted Create and Read extensions for grass cover erosion outwards failure mechanism - Removed all files and functionality related to creating/reading the HydraulicBoundaryLocationEntity and the HydraulicBoundaryLocationOutputEntity for specific grass cover erosion outwards failure mechanismWTI-1657
Adjusted ReadExtensions for grass cover erosion outwards failure mechanism - Adjusted the AssessmentSectionReadExtensions --> should be responsible for configuring the failuremechanism before reading failure mechanism related data -- Cleaned up tests and fixed failing onesWTI-1657
Adjusted CreateExtensions for grass cover erosion outwards failure mechanism: - Adjusted tests to verify that the HBL Calculations are written to the correct entitiesWTI-1657
Cleanup: - Added missing asserts upon migration - Renamed the query generator functions to better distinct between HBL calculations that are migrated and HBL calculations that are newly createdWTI-1656
Adjusted migration script and asserts: - Migrated the hydraulic location output based on the normative norm and mapped them onto the new HydraulicLocationOutputEntity and the corresponding HydraulicLocationCalculationEntitiesWTI-1656
Adjusted migration script and asserts: - Migrated the hydraulic location input based on the normative norm and mapped them onto the new HydraulicLocationCalculationEntity - Refactored testNote: output is not migrated yetWTI-1656
Adjusted migration script and asserts: - Migrated the hydraulic location calculations and mapped them onto the assessment section conform the new design of the database - Removed obsolete queries from the generatorNote: output is not migrated yetWTI-1656
Adjusted StorageIntegrationTest: - Removed asserting calculation input on the location calculations (due to deprecated feature) - Added assertion logic on the assessment section insteadWTI-1656
Finalized database design: - Added comments to indicate which FK represents which type of calculation - Adjusted read and create extensions on the assessment section to maintain consistency with the commentsWTI-1656
Cleaned up database related files: - Removed trigger from association table between the calculation collection and the calculation - Renamed names of foreign key according to the naming conventions - Added uniqueness constraint for: -- the association table on the calculations -- the uniqueness of the FK entries of the assessment section entity - Removed two obsolete table entities from the .eap file - Updated the .sql file --> added HydraulicBoundaryLocationCalculationCollection entities should be autonumbered - Removed obsolete lines from the edmx.diagram - Added additional load logic for the PartialRingtoetsEntities in order to fully load the projectWTI-1656
Adjusted Read extensions: - Adjusted the AssessmentSection read extensions to set the calculations based on the HydraulicBoundaryLocationCalculations it contains.Note: mapping of the calculation is not final yetWTI-1656
Introduced Read extensions: - Introduced a HydraulicLocationCalculationCollection read extensions to set the values on a hydraulic location calculation collection based on the calculation entities contained by the HydraulicLocationCalculationCollectionEntity.WTI-1656
Adjusted create extensions: - Adjusted the AssessmentSection create extensions to set the HydraulicLocationCalculation entities based on the calculations it contains.Note: mapping of the calculation is not final yetWTI-1656
Introduced create extensions: - Introduced a the HydraulicLocationCalculationCollection create extensions to create a hydraulic location calculation collection entity and its containing hydraulic boundary location calculations.WTI-1656
Introduced read extensions: - Introduced the HydraulicLocationCalculation read extensions to set the values on a calculation object based on the information of a HydraulicLocationEntity.WTI-1656
Adjusted create extensions: - Adjusted the HydraulicLocationCalculation create extensions such that they retrieve the same HydraulicLocation entity once registered.WTI-1656
