> Switching to 1.2.2 and using connect_args = {'use_unicode':
> False,'charset': 'utf8'} works fine for me.
Hi Jürgen,
I'm curious; if you upgraded to 1.2.2, does the issue persist if you
stop using "connect_args = {'use_unicode': False,'charset': 'utf8'}"?
Bo
On Thu, Sep 18, 2008 at 3:07 AM,
Thank you.
Switching to 1.2.2 and using connect_args = {'use_unicode':
False,'charset': 'utf8'} works fine for me.
Jürgen
Michael Bayer schrieb:
> I believe this is the ticket:
>
> http://sourceforge.net/tracker/index.php?func=detail&aid=1592353&group_id=22307&atid=374932
>
> its a little ambig
I believe this is the ticket:
http://sourceforge.net/tracker/index.php?func=detail&aid=1592353&group_id=22307&atid=374932
its a little ambiguous as to its resolution, maybe I'll ask Shannon
what his most recent experiences were.
On Sep 17, 2008, at 12:03 PM, Bo Shi wrote:
>
> While research
While researching which version to deploy, I had run into a thread
post _claiming_ that 1.2.2 had a critical bug which was documented in
the fedora bugzilla. I never managed to actually find said bug but it
scared me off. The reason we went with 1.2.1p2 was because it was the
version the Django
On Sep 17, 2008, at 10:50 AM, Bo Shi wrote:
>
> I ran into a similar issue using MySQL-python-1.2.1_p2-1 (mysqldb)
> with SA 0.4.2p3-1.
I would advise upgrading to MySQL-python 1.2.2. I believe some utf-8
issues have been fixed.
--~--~-~--~~~---~--~~
You re
I ran into a similar issue using MySQL-python-1.2.1_p2-1 (mysqldb)
with SA 0.4.2p3-1.
http://www.mail-archive.com/sqlalchemy@googlegroups.com/msg00373.html
might shed some more light on this issue which might be a double
encoding problem?
Here is the subset of relevant keyword arguments we use w
