#2635: [patch] Updates for MySQL backend
--------------------------------------------------+-------------------------
Reporter: Andy Dustman <[EMAIL PROTECTED]> | Owner:
mtredinnick
Status: closed | Component:
Database wrapper
Version: SVN | Resolution:
fixed
Keywords: | Stage:
Ready for checkin
Has_patch: 1 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
--------------------------------------------------+-------------------------
Comment (by beegee):
Replying to [comment:18 derelm]:
> that didn't help.
>
> but i noticed that the version check doesn't work as expected (at least
not with Debian Sarges MySQLdb version 1.2.1g2). see #3747
>
> and seeing that that version isn't supported at all, my complaint about
the umlauts not working is invalid.
>
> so i will need to stick with r4723.
Revision 4724 is giving me headaches for several hours now. My dev
environment has no problem at all with rev 4724. But, in my production
environment utf8 characters are not handled correctly. It leads to decode
errors and utf8 character displayed as , instead of a nice character. My
dev enviroment has >>> print MySQLdb.version_info = (1, 2, 1, 'final', 2)
and my production enviroment has >>> print MySQLdb.version_info = (1, 2,
1, 'gamma', 3) (Debian). I will try upgrading MySQLdb in my production
environment.
--
Ticket URL: <http://code.djangoproject.com/ticket/2635#comment:21>
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
-~----------~----~----~----~------~----~------~--~---
