#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 Keywords: | Stage: Unreviewed Has_patch: 0 | ---------------------------+------------------------------------------------ I recently had an error in a query in a context processor. When I tried to go to a certain page, I got the error:
"No CollabProject matches the given query". And practically no other information. No trackbacks or anything. No indication of which file the error was in. Just that message and a 404. I kept checking and couldn't find any error in my view. I even confirmed that the view executed to the end. It was only by chance that I discovered the error in the context processor. Isn't there a way to have it such that if the error occurs in a context processor, it can point to the line in the context processor that had the bad query? BTW, by bad query I mean a valid query that doesn't return any objects in the database. I suspect this may be a problem with such a query in a middleware, but did not experiment. -- Ticket URL: <http://code.djangoproject.com/ticket/8772> 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 -~----------~----~----~----~------~----~------~--~---
