#7780: get returns multiple objects when model includes a ManyToManyField in
the
default ordering
-------------------------------------+--------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: nobody
Status: closed | Milestone:
Component: Uncategorized | Version: SVN
Resolution: invalid | Keywords:
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-------------------------------------+--------------------------------------
Changes (by mtredinnick):
* status: new => closed
* needs_better_patch: => 0
* resolution: => invalid
* needs_tests: => 0
* needs_docs: => 0
Comment:
"Doctor it hurts when I do this".. "Then don't do that, sir".
As noted in the documentation for ordering, it is legal to include multi-
valued fields because there are some situations where it returns sensible
results, so prohibiting them always leads to undesired restrictions. That
does not mean that including them is a sensible thing to do and you should
always never do it.
This isn't a bug in Django because the functionality is needed in some
cases. The solution is not to include that field in your default ordering
(ordering by multiple valued results hardly ever makes sense).
--
Ticket URL: <http://code.djangoproject.com/ticket/7780#comment:1>
Django Code <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 [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
