[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[GNUe] RE: gnue-common bug: mysqldbdrv.py with MySQLdb 1.2.2 always deco
From: |
Johannes Vetter |
Subject: |
[GNUe] RE: gnue-common bug: mysqldbdrv.py with MySQLdb 1.2.2 always decodes query result using latin1 |
Date: |
Thu, 12 Jul 2007 10:22:13 +0200 |
Hi Oleg,
I'm lacking a MySQLdb 1.2.2 driver as well as a MySQL 5 Server here, so
I cannot reproduce your problem or verify your patch.
But the value for "self._encoding" is taken from your connections.conf.
If there is no such value provided, it will default to "utf-8". This
value will be used for all encoding and decoding of the unicode values
in use.
So if you appear to have everything encoded/decoded in latin-1 you're
likely having an "encoding=latin-1 (or iso8859-1)" in your
connections.conf (for that connection).
Aside from that, your patch suggests setting the charset via keyword
instead of performing an explicit "SET NAMES" when using a MySQL 5+. As
you've mentioned this works fine with the MySQLdb 1.2.2 driver. Can you
check this with a MySQLdb 1.2.1 driver ? If it works there too, we can
integrate your patch.
Thanks for your suggestions,
Have a nice day
Johannes
--
BYTEWISE Software GmbH Tel +43 (5577) 63377
i.A. Johannes Vetter Fax +43 (5577) 63381
A-6890 Lustenau, Enga 2 http://www.bytewise.at
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Individuelle Datenbanklösungen für GNU/Linux, Windows und
Mac OSX: http://www.bytewise.at/leistungen/gnue-indiv.html
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
- [GNUe] RE: gnue-common bug: mysqldbdrv.py with MySQLdb 1.2.2 always decodes query result using latin1,
Johannes Vetter <=