We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
addColumn ignores deleteCascade:
generates:
"ALTER TABLE x.run_data ADD PARENT_RUN_ID VARCHAR(36)" "ALTER TABLE x.run_data ADD CONSTRAINT RUN_DATA_FK02 FOREIGN KEY (PARENT_RUN_ID) REFERENCES x.RUN_DATA (RUN_ID)"
deleteCascade from inside addTable and addForeignKeyConstraint generate the correct SQL, e.g.:
"ALTER TABLE x.RUN_DATA ADD CONSTRAINT RUN_DATA_FK02 FOREIGN KEY (PARENT_RUN_ID) REFERENCES x.RUN_DATA (RUN_ID) ON DELETE CASCADE"
The text was updated successfully, but these errors were encountered:
Hi @rsaccoccio Thanks for writing up this issue. There is not attribute deleteCascade on a column type in liquibase. https://docs.liquibase.com/change-types/community/add-column.html?Highlight=add%20column#Informa
Sorry, something went wrong.
I have a fix in #1970 for this
Successfully merging a pull request may close this issue.
addColumn ignores deleteCascade:
tableName: run_data
columns:
name: PARENT_RUN_ID
type: VARCHAR(36)
constraints:
foreignKeyName: RUN_DATA_FK02
references: RUN_DATA(RUN_ID)
deleteCascade: true
generates:
"ALTER TABLE x.run_data ADD PARENT_RUN_ID VARCHAR(36)"
"ALTER TABLE x.run_data ADD CONSTRAINT RUN_DATA_FK02 FOREIGN KEY (PARENT_RUN_ID) REFERENCES x.RUN_DATA (RUN_ID)"
deleteCascade from inside addTable and addForeignKeyConstraint generate the correct SQL, e.g.:
baseColumnNames: parent_run_id
baseTableName: run_data
constraintName: run_data_fk02
onDelete: CASCADE
referencedColumnNames: run_id
referencedTableName: run_data
generates:
"ALTER TABLE x.RUN_DATA ADD CONSTRAINT RUN_DATA_FK02 FOREIGN KEY (PARENT_RUN_ID) REFERENCES x.RUN_DATA (RUN_ID) ON DELETE CASCADE"
The text was updated successfully, but these errors were encountered: