fix addForeignKeyConstraint

[ghazwarhili]

No description provided.

[etiennehomer]

Suggested change

	<addForeignKeyConstraint baseColumnNames="operational_limits_groups_id" baseTableName="two_windings_transformer_modification_operational_limits_groups" constraintName="operational_limits_groups_twt_modification_id_fk" deferrable="false" initiallyDeferred="false" referencedColumnNames="uuid" referencedTableName="operational_limits_group_modification" validate="true"/>
	<addForeignKeyConstraint baseColumnNames="operational_limits_groups_id" baseTableName="two_windings_transformer_modification_operational_limits_groups" constraintName="operational_limits_groups_2wt_modification_id_fk" deferrable="false" initiallyDeferred="false" referencedColumnNames="uuid" referencedTableName="operational_limits_group_modification" validate="true"/>

[ghazwarhili]

done

[ghazwarhili]

@onetomany
@joincolumn(name = "equipment_modification_id")
The OneToMany owns the FK since it's declared on the parent side
On delete:

1. UPDATE free_property SET equipment_modification_id = NULL WHERE equipment_modification_id = :id;
   (because the FK is managed by the parent, so we must break it before the delete)
2. DELETE FROM free_property WHERE id = ***;
3. DELETE FROM modification WHERE id = ***;
   => Results in 2 UPDATEs (UPDATE generated before the DELETE)

With:
FreePropertyEntity:
@manytoone
@joincolumn(name = "equipment_modification_id")
private ModificationEntity modification;

EquipmentModificationEntity:
@onetomany(mappedBy = "modification")
private List properties;

=> The ManyToOne owns the FK
On delete:
DELETE FROM free_property WHERE equipment_modification_id = :id
(the FK is managed by the child, so no need to set it to NULL)

Since we have @OrderColumn(name = "insert_position") an UPDATE is generated to update and reindex the list before DELETE

[sonarqubecloud]

Quality Gate failed

Failed conditions
72.7% Coverage on New Code (required ≥ 80%)

See analysis details on SonarQube Cloud