#11670: Model fields named 'year', 'month', 'gt', 'lt' etc. get mistaken for
lookup
types in lookups across relations
-------------------------------------+-------------------------------------
Reporter: andy@… | Owner:
Type: Bug | Status: new
Component: Database layer | Version: SVN
(models, ORM) | Resolution:
Severity: Normal | Triage Stage: Accepted
Keywords: | Needs documentation: 0
Has patch: 1 | Patch needs improvement: 1
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by julien):
The patch above is a slight improvement on 11670.field-lookup-
collisions.2.diff, as the full lookup resolution now only occurs if the
last part isn't a lookup type. That means there wouldn't be any extra
computation for the most common lookups.
Since it's a bit late before 1.4 gets released to do a full refactor as
discussed earlier, I suggest we start by fixing the bug using that latest
patch, and then look into a proper refactor later for 1.5.
--
Ticket URL: <https://code.djangoproject.com/ticket/11670#comment:24>
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
