-
Notifications
You must be signed in to change notification settings - Fork 2.9k
#19680 fix deletion dependency order for GenericRelations #19681
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
Conversation
jnovinger
left a comment
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.
Just had the one question. Otherwise, this looks pretty sane and well contained.
| # | ||
|
|
||
| class ChangeLoggingMixin(models.Model): | ||
| class ChangeLoggingMixin(DeleteMixin, models.Model): |
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.
@arthanson , just to be clear, we only want to employee this mechanism for ChangedLoggingMixin and no other, correct?
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.
Yes, it only matters in that case. This changes the order that the delete signal handlers are sent out, but the only reason we care about that is what order the ObjectChange records are written out, so this only effects models derived from ChangeLoggingMixin.
Fixes: #19680