On Tue, Mar 2, 2010 at 7:05 PM, Brandon <[email protected]> wrote:
> No error. I'm guessing Django doesn't populate connection.queries
> when it isn't in debug mode?
>
Right.
> This would definitely work for production, but what other options do I
> have for development? It would be a huge step up for us to be able to
> work in an interactive shell and see what queries were run during
> those actions.
>
Try changing this line:
File
"/usr/local/lib/python2.5/site-packages/django/db/backends/__init__.py",
line 209, in <lambda>
to_unicode = lambda s: force_unicode(s, strings_only=True)
to:
to_unicode = lambda s: force_unicode(s, strings_only=True,
errors='replace')
(You might want to switch to running from a copy of Django not installed in
site-packages rather than start changing the official installed version.)
That might avoid the problem, though the params data stored in connection
queries won't necessarily be too helpful.
I think there's an argument to be made that errors='replace' ought to be
what is specified there, just because the gathering of debug data should not
cause an exception to be raised. So that might be a relatively simple fix
that could be put in easily, if it is actually helpful for your case.
Karen
--
You received this message because you are subscribed to the Google Groups
"Django users" 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-users?hl=en.
