On 8/28/07, George Vilches <[EMAIL PROTECTED]> wrote: ... > Something seems very wrong about this situation, that debugging could > cause another query to execute (especially an unintended query), but I > don't know what the correct way to go about fixing or preventing it. > I've tried a bunch of things to stop the QuerySets from evaluating when > the local vars are being printed, but haven't been able to come up with > anything much. Is there a good way to prevent this issue in the 500 > template?
As a ham-handed fix, django.views.debug, where it pushes the frame locals into 'vars' , could remove instances of queryset. Alternatively, it could substitute the generated sql for the queryset itself. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" 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-developers?hl=en -~----------~----~----~----~------~----~------~--~---
