#22064: Invalid related_name passes silently
-------------------------------------+-------------------------------------
Reporter: mondone | Owner: aericson
Type: | Status: closed
Cleanup/optimization | Version: master
Component: Database layer | Resolution: fixed
(models, ORM) | Triage Stage: Accepted
Severity: Normal | Needs documentation: 0
Keywords: | Patch needs improvement: 0
Has patch: 1 | UI/UX: 0
Needs tests: 0 |
Easy pickings: 1 |
-------------------------------------+-------------------------------------
Changes (by André Ericson <de.ericson@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"1e5e2a470768549117ac4696ce3e8b4e51d65664"]:
{{{
#!CommitTicketReference repository=""
revision="1e5e2a470768549117ac4696ce3e8b4e51d65664"
Fixed #22064 -- Add check for related_name
Validates that related_name is a valid Python id or ends with a '+' and
it's not a keyword. Without a check it passed silently leading to
unpredictable problems.
Thanks Konrad Świat for the initial work.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/22064#comment:12>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.8c4d54640a38ce86b7b02fbdf75ea603%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.