Skip to content

Consider removal of related_name #3

@unbracketed

Description

@unbracketed

I experienced in a project that the admin can do screwy things when trying to delete objects that have GFK relationships where related_name is used somewhere.

These tickets seem to confirm the behavior we saw:
https://code.djangoproject.com/ticket/16913
https://code.djangoproject.com/ticket/16920

Currently related_name is used in models.py setup_generic_relations().

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions