Fix destroying belongs_to associations for CPK #48385
Merged
Conversation
This file contains 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
This commit handles destroying CPK associations when autosave is set and the parent association is marked for destruction. It does so by ensuring that all parts of the foreign key (the parent's CPK) are set to nil before destroying the parent record.
gmcgibbon
approved these changes
Jun 2, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Motivation / Background
This PR handles destroying CPK associations when autosave is set and the parent association is marked for destruction.
Detail
This Pull Request changes the codepath in
#save_belongs_to_associationthat handles destroying the parent association to handle a composite foreign key (the parent having a composite primary key). It does so by ensuring that all parts of the foreign key (the parent's CPK) are set to nil before destroying the parent record.Checklist
Before submitting the PR make sure the following are checked:
[Fix #issue-number]