#36973: fields.E348 check should check against the accessor_name instead of the
model name
-------------------------------------+-------------------------------------
Reporter: nick.ma@… | Owner: Clifford
| Gama
Type: Bug | Status: closed
Component: Database layer | Version: 6.0
(models, ORM) |
Severity: Release blocker | Resolution: fixed
Keywords: System checks, | Triage Stage: Ready for
fields.E348, related_name | checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Jacob Walls <jacobtylerwalls@…>):
In [changeset:"4eb38f6994f233feeac5852cbee2ae6663a9b1ef" 4eb38f6]:
{{{#!CommitTicketReference repository=""
revision="4eb38f6994f233feeac5852cbee2ae6663a9b1ef"
[6.0.x] Fixed #36973 -- Made fields.E348 check detect further clashes
between managers and related_names.
Clashes were only detected for self-referential relationships, i.e.
ForeignKey("self").
Refs #22977. Bug in 6888375c53476011754f778deabc6cdbfa327011.
Thanks JaeHyuckSa for the thorough review!
Backport of fcf916884d25ed430bd7cedaea2b10035c2aa3b6 from main.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/36973#comment:10>
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/0107019d4fc36958-ed4130c5-818e-47f0-be87-6f3ec3be4be5-000000%40eu-central-1.amazonses.com.
