On Wed, Dec 7, 2011 at 9:59 PM, Vinay Sajip <vinay_sa...@yahoo.co.uk> wrote:
> On Dec 7, 8:38 pm, Ian Clelland <clell...@gmail.com> wrote:
>
> > Thoughts?
>
> A further update: of my 24 failures, 17 are in multiple_database, as
> are 3 failures. But I get the same errors with unpatched Django 2.x
> running with the standard 2.x MySQLdb adapter, so it might be
> something to do with my MySQL configuration.
>
>
There also seem to be a number of unicode-related errors there (mixed
collations; unrecognized characters) -- Could that be related to the lines
in your patched mysql/base.py:
if not PY3:
kwargs['use_unicode'] = True
use_unicode used to be unconditional on the database connection; now you've
removed it, but just for Python 3.
--
Regards,
Ian Clelland
<clell...@gmail.com>
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en.
