#9252: IncorrectLookupParameters not being raised in admin get_query_set
-----------------------------------------------+----------------------------
Reporter: leanmeandonothingmachine | Owner: nobody
Status: new | Milestone: post-1.0
Component: django.contrib.admin | Version: 1.0
Resolution: | Keywords:
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-----------------------------------------------+----------------------------
Comment (by kmtracey):
Clarification of how to recreate the problem would be helpful here. I'm
thinking you are talking about things like manually tweaking a filter
lookup parameter in the url. Getting it wrong used to just get you
redirected to the unfiltered change list page with a special error
parameter in the url that gave you a clue (if you knew what it meant) what
had happened. Now I see that doesn't happen, instead you get, for
example, a !FieldError raised. Is this what you are talking about or
something else?
--
Ticket URL: <http://code.djangoproject.com/ticket/9252#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-updates@googlegroups.com
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
-~----------~----~----~----~------~----~------~--~---
