Skip to content

Conversation

@arthanson
Copy link
Collaborator

Fixes: #19680

Copy link
Member

@jnovinger jnovinger left a 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):
Copy link
Member

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?

Copy link
Collaborator Author

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.

@arthanson arthanson marked this pull request as ready for review June 13, 2025 20:03
@arthanson arthanson changed the title DRAFT: #19680 fix deletion dependency order for GenericRelations #19680 fix deletion dependency order for GenericRelations Jun 13, 2025
@arthanson arthanson requested a review from jnovinger June 13, 2025 20:03
@jnovinger jnovinger merged commit 6a62867 into main Jun 13, 2025
10 checks passed
@jnovinger jnovinger deleted the 19680-object-change branch June 13, 2025 21:09
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 14, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

ObjectChange incorrect ordering for GenericRelation references

3 participants