#14366: Model.objects.none().values(...).anything() is broken
---------------------------------------------------+------------------------
Reporter: carljm | Owner: nobody
Status: new | Milestone:
Component: Database layer (models, ORM) | Version: 1.2
Resolution: | Keywords:
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Comment (by carljm):
I looked around for a while to see if I could find a way to pin this on
multi-db, but no luck. Turns out it's just a simple matter of
EmptyQuerySet._clone() ignoring its "setup" arg instead of passing it on
to QuerySet._clone(). Patch with test attached, also at
http://github.com/carljm/django/compare/master...ticket_14366
--
Ticket URL: <http://code.djangoproject.com/ticket/14366#comment:2>
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.
