#22377: SQL Logging throws an exception when fields have utf-8 characters
-------------------------------------+-------------------------------------
Reporter: rolanvc@… | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 1.6
(models, ORM) | Resolution:
Severity: Normal | Triage Stage:
Keywords: sql logging for | Unreviewed
utf-8 | Needs documentation: 0
Has patch: 0 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by kahnert):
It's absolutely sure that all content in `header_vals` is correctly
encoded, since it's read from utf-8 encoded CSV files. All content columns
are safe-decodeded to unicode after reading. If I turn the DebugCursor
off, all content gets into the DB and is correctly displayed when read
from the DB.
But you're right, I could not create a test case in which
{{{
from __future__ import unicode_literals
logging.debug('(%.3f) %s; args=%s' % (duration, sql, params),
extra={'duration': duration, 'sql': sql, 'params': params}
)
}}}
throws an error. Even if I put wrong encoded strings into the `params`
dict.
May it be possible that the actual DecodingError is produced by some
logging handler or formatter?
Does the used db connector make a difference?
--
Ticket URL: <https://code.djangoproject.com/ticket/22377#comment:5>
Django <https://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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/075.decb0a4be349db9bd276f253eea0ec52%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
