-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
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
Redefine on delete cascades #450
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Really good! Maybe just combine the migrations or name them to explain why they are separate?
082df01
to
09effca
Compare
Deletes on lookup code tables should not propagate delete on a table referencing it.
09effca
to
ba97c14
Compare
I intentionally kept the commits small and logically separated. |
Included also tests to check cascade deletions using both ORM and SQL. |
This is based on #452, merge that before this one.
Removed cascade delete from:
Added cascade delete to:
Plan object tables has still on_delete=NO ACTION on their foreign keys to the plan table to prevent accidentally deleting the whole plan with objects.
Resolves #436, GispoCoding/arho-feature-template#193