#9222: Allow callable queryset in generic views
-------------------------------------------------+--------------------------
Reporter: [EMAIL PROTECTED] | Owner: nobody
Status: closed | Milestone: post-1.0
Component: Generic views | Version: SVN
Resolution: wontfix | Keywords:
Stage: Unreviewed | Has_patch: 1
Needs_docs: 0 | Needs_tests: 1
Needs_better_patch: 0 |
-------------------------------------------------+--------------------------
Changes (by mtredinnick):
* status: new => closed
* resolution: => wontfix
Comment:
Thanks for the patch, but we aren't going to do this. The solution to any
problem involving wanting to pass some kind of customised queryset to a
generic view is to create your own view that creates the right queryset
and then calls the generic view.
Although each little addition to generic views only feels like a few
lines, it is a few extra lines each time that requires extra maintenance,
prompts extra questions on the users list, adds extra documentation,
requires extra tests, etc. It basically adds to the overhead when it's a
three line function when the user needs it (which usually results in
cleaner code, too, since it's clear what you're trying to do).
--
Ticket URL: <http://code.djangoproject.com/ticket/9222#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 [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
-~----------~----~----~----~------~----~------~--~---
