#23940: ORM should allow model fields named "exact"
-------------------------------------+-------------------------------------
Reporter: zhiyajun11 | Owner: Simon
| Charette <charette.s@…>
Type: Bug | Status: closed
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Simon Charette <charette.s@…>):
* owner: => Simon Charette <charette.s@…>
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"eb4cdfbdd64a95b303eaaa40a070521aa58362fd"]:
{{{
#!CommitTicketReference repository=""
revision="eb4cdfbdd64a95b303eaaa40a070521aa58362fd"
Fixed #23940 -- Allowed model fields to be named `exact`.
An explicit `__exact` lookup in the related managers filters
was interpreted as a reference to a foreign `exact` field.
Thanks to Trac alias zhiyajun11 for the report, Josh for the
investigation,
Loïc for the test name and Tim for the review.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/23940#comment:25>
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/068.07f7038e7f9c4e408f50aad30624aa27%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
