#36973: fields.E348 check should check against the accessor_name instead of the
model name
-------------------------------------+-------------------------------------
Reporter: nick.ma@… | Owner: Shubh Rai
Type: Bug | Status: assigned
Component: Database layer | Version: 6.0
(models, ORM) |
Severity: Normal | Resolution:
Keywords: System checks, | Triage Stage: Accepted
fields.E348, related_name |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Clifford Gama):
* easy: 1 => 0
* stage: Unreviewed => Accepted
Comment:
While investigating this ticket, I discovered that the patch added in
#22977 only identifies a clash between an accessor and a manager if the
relationship is self-referential. The attempt to fix that issue made it
easier to understand the issue reported here. I opened an alternative PR
to fix both issues.
--
Ticket URL: <https://code.djangoproject.com/ticket/36973#comment:3>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/0107019cd89f3b1d-3a2e9c34-9775-4c82-8c71-77f59acfe02f-000000%40eu-central-1.amazonses.com.
