#14766: ordering by a field that does not exists returns an empty QuerySet
---------------------------------------------------+------------------------
Reporter: robhudson | Owner: nobody
Status: reopened | Milestone:
Component: Database layer (models, ORM) | Version: 1.2
Resolution: | Keywords:
sprintdec2010 order_by
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Changes (by Aramgutang):
* keywords: order_by => sprintdec2010 order_by
* stage: Unreviewed => Accepted
Comment:
The actual issue appears to be that the validation of the arguments to
order_by doesn't occur until the query is about to be evaluated. So `q =
Model.objects.order_by('monkeys')` doesn't raise a FieldError, but
`list(Model.objects.order_by('monkeys'))` does. However, the validation
occurs before the query is passed to the database, which is comforting.
d0ugal: it makes sense for count() to work, since order_by is ignored
completely when getting a count.
--
Ticket URL: <http://code.djangoproject.com/ticket/14766#comment:8>
Django <http://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-upda...@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.
