[Sylvie-P]

HCK-18408 [AMEX] FE still generates the foreign key of a deactivated relationship

## Content

Jira: HCK-18408

When a relationship is deactivated but both tables and their key columns are activated, forward-engineering still generated the foreign key as an active statement. It should be commented out, like other deactivated objects.

Technical details

• Studio passes the relationship flag to the DDL provider as isActivated, but createForeignKeyConstraint only looked at the tables and the key columns.
• The returned isActivated now also takes the relationship flag, the same way the PostgreSQL plugin does it. The columns list is still built like before.
• !== false is used so a missing flag (old models) keeps the foreign key activated.
• Redshift has only createForeignKeyConstraint, there is no createForeignKey here.
• getTableConstraints added every foreign key to the CREATE TABLE without checking isActivated. Deactivated foreign keys are now put in a commented block after the active constraints, like deactivated columns.
• Tested in Studio on Redshift.
• Same fix is done in SQLServer, Oracle, MySQL, MariaDB, Db2, Db2-zOS and Redshift.

Made with Cursor

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud