#4179: MySQL backend has MySQL-4.0 incompatbiility
---------------------------+------------------------------------------------
Reporter: mtredinnick | Owner: adrian
Status: new | Component: Database wrapper
Version: SVN | Resolution:
Keywords: | Stage: Accepted
Has_patch: 0 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
---------------------------+------------------------------------------------
Comment (by Andy Dustman <[EMAIL PROTECTED]>):
{{{use_unicode=True}}} has absolutely no effect on objects passed to
{{{execute()}}}. It only affects how text-ish columns are returned from
the database. If True, varchar, text, etc., are returned as unicode
objects. If False, they are returned as strings. Regardless of the
setting, you can always pass unicode objects as parameters, and they are
encoded into strings with the connection's character set. So you can
always throw unicode objects at MySQLdb; {{{use_unicode}}} only determines
whether or not MySQLdb throws unicode objects at '''you'''.
The last time I tried the unit tests (at !PyCon), turning on
{{{use_unicode=True}}} ''did'' break some unit tests, but only for
superficial reasons, i.e. it was comparing equality for two lists, and one
lists had strings and the other unicode, so they compared as unequal.
--
Ticket URL: <http://code.djangoproject.com/ticket/4179#comment:4>
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
-~----------~----~----~----~------~----~------~--~---
