#8772: Errors in queries in context processors give a very unhelpful error page.
------------------------------------+---------------------------------------
Reporter: Beetle_B | Owner: nobody
Status: new | Milestone:
Component: Uncategorized | Version: SVN
Resolution: | Keywords:
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
------------------------------------+---------------------------------------
Changes (by Beetle_B):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
In retrospect, I realized it wasn't an error, as I was using a
get_object_or_404. So the function was doing exactly what it should -
returning a 404.
Nevertheless, it would be nice if when this happens, it could return the
location of the query that did not find any object (when DEBUG=True). It's
help in debugging.
--
Ticket URL: <http://code.djangoproject.com/ticket/8772#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
-~----------~----~----~----~------~----~------~--~---
