Validate new Patient foreign key relationships#6640
Open
alistair-white-horne-tng wants to merge 1 commit intoalistair/patient-cascade-on-deletefrom
Open
Validate new Patient foreign key relationships#6640alistair-white-horne-tng wants to merge 1 commit intoalistair/patient-cascade-on-deletefrom
Patient foreign key relationships#6640alistair-white-horne-tng wants to merge 1 commit intoalistair/patient-cascade-on-deletefrom
Conversation
alistair-white-horne-tng
force-pushed
the
alistair/patient-cascade-on-delete
branch
from
3e5d523 to
7105c17
Compare
alistair-white-horne-tng
force-pushed
the
alistair/patient-cascade-on-delete-validate
branch
3 times, most recently
from
0817678 to
799a530
Compare
alistair-white-horne-tng
force-pushed
the
alistair/patient-cascade-on-delete
branch
from
7105c17 to
4088257
Compare
thomasleese
approved these changes
Apr 20, 2026
alistair-white-horne-tng
force-pushed
the
alistair/patient-cascade-on-delete
branch
from
4088257 to
3243141
Compare
alistair-white-horne-tng
force-pushed
the
alistair/patient-cascade-on-delete-validate
branch
from
799a530 to
0bafd56
Compare
alistair-white-horne-tng
force-pushed
the
alistair/patient-cascade-on-delete
branch
4 times, most recently
from
afe7139 to
fd7c15e
Compare
After adding "cascade on delete" to these `Patient` FK relationships, we need to validate them. We can't do this as part of the same migration because it's likely to cause a long table lock, which is unacceptable in production. Hence, this needs to be included in the subsequent release. Jira-Issue: MAV-7065
alistair-white-horne-tng
force-pushed
the
alistair/patient-cascade-on-delete-validate
branch
from
0bafd56 to
06e3450
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Must be in the release after #6638
After adding "cascade on delete" to these
PatientFK relationships, we need to validate them.We can't do this as part of the same migration because it's likely to cause a long table lock, which is unacceptable in production. Hence, this needs to be included in the subsequent release.
MAV-7065