## Environment
**Liquibase Version**: 4.3.1

**Liquibase Integration & Version**: n/a

**Liquibase Extension(s) & Version**: n/a 

**Database Vendor & Version**: Oracle and MSSQL

**Operating System Type & Version**: n/a

## Description
If you have an `addForeignKeyConstraint` change with attribute `deleteCascade="true"` it is simply ignored.
This code: https://github.com/liquibase/liquibase/blob/43ed0e54adedc5f12c7933b998550e777d9b683d/liquibase-core/src/main/java/liquibase/change/core/AddForeignKeyConstraintChange.java#L195-L199 suggests that it should be automatically translated to `onDelete="CASCADE"` which would make sense, but it is not.
It currently is simply ignored.


);
                }
                if (getValidate() != null) {
                    result.assertCorrect(getValidate().equals(snapshot.shouldValidate()), "validate incorrect");
                }
            }
            return result;
        } catch (Exception e) {
            return result.unknown(e);
        }
    }
    @Override
    public String getConfirmationMessage() {
        return "Foreign key constraint added to " + getBaseTableName() + " (" + getBaseColumnNames() + ")";
    }
    /**
     * @deprecated No longer supported in 3.0
     */
    @Deprecated
    public Boolean getReferencesUniqueColumn() {
        return null;
    }
    public void setReferencesUniqueColumn(Boolean referencesUniqueColumn) {
    }
    @Override
    public String getSerializedObjectNamespace() {
        return STANDARD_CHANGELOG_NAMESPACE;
    }
}