#23940: Disallow/warn on fields named exact
-------------------------------------+-------------------------------------
Reporter: zhiyajun11 | Owner: nicwest
Type: New feature | Status: assigned
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by collinanderson):
Marcus and I were talking on IRC about this.
- Is this issue specific to exact? Are _all_ lookups a problem? Looking at
the code it's probably an issue for `iexact` and `isnull` also.
- Would it be possible to support having a field named "exact"?
--
Ticket URL: <https://code.djangoproject.com/ticket/23940#comment:14>
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.efd13a2ef167c94d07d4b1ce24351d52%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
