Sounds good. Thanks Jason!
On 8/20/07, jason kirtland [EMAIL PROTECTED] wrote:
Arun wrote:
So in short if I specify use_unicode=True at the SA engine level
then I can skip specifying use_unicode and specify only
charset=utf8 at mysqldb level ?
If you configure this DB-API driver for
So in short if I specify use_unicode=True at the SA engine level then I can
skip specifying use_unicode and specify only charset=utf8 at mysqldb level ?
On 8/19/07, jason kirtland [EMAIL PROTECTED] wrote:
Arun Kumar PG wrote:
Ok, you need to get that charset to the driver. Try removing
Arun wrote:
So in short if I specify use_unicode=True at the SA engine level
then I can skip specifying use_unicode and specify only
charset=utf8 at mysqldb level ?
If you configure this DB-API driver for all-Unicode (which is what
happens when you only give it a 'charset') all strings will
why do we want to say use_unicode=0 instead or use_unicode=True here?
On 8/16/07, jason kirtland [EMAIL PROTECTED] wrote:
Ok you need to get tArun wrote:
I am using mysqldb-1.2.2. I am passing 'SET NAMES' to connect
method as a value for init_command parameter. All tables have
utf8
Arun Kumar PG wrote:
Ok, you need to get that charset to the driver. Try removing SET
NAMES from your init_command, and instead pass charset=utf8 and
use_unicode=0 in your database connection URL.
why do we want to say use_unicode=0 instead or use_unicode=True here?
You can
Whooops. the problem in coming on the box which is running mysqldb1.2.0.
Actually it's a non-upgraded server with mysqldb 1.2.0. I was looking at the
code on my box which contains 1.2.2.
But I am sure that even with mysqldb 1.2.0 the existing SA version was
working fine. and that's why
Arun Kumar PG wrote:
Hi All,
Recently I upgraded to the version 3.9 of SA. Post that whenever I am
trying to save characters in different language in the table I am
getting the below exception:
File /src/sqlalchemy/engine/base.py,
line 601, in _execute
raise
All tables are having a charset of utf8. Additionally, I am issuing SET
NAMES 'utf8' statement as a part of connection establishment.
Anything that is wrong here or missing ?
On 8/15/07, jason kirtland [EMAIL PROTECTED] wrote:
Arun Kumar PG wrote:
Hi All,
Recently I upgraded to the
Arun Kumar PG wrote:
All tables are having a charset of utf8. Additionally, I am issuing SET
NAMES 'utf8' statement as a part of connection establishment.
Anything that is wrong here or missing ?
Are you updating the connection character set in the driver as well
after issuing SET NAMES?
are you using convert_unicode=True and/or the Unicode type ?
On Aug 15, 2007, at 12:01 PM, Arun Kumar PG wrote:
All tables are having a charset of utf8. Additionally, I am issuing
SET NAMES 'utf8' statement as a part of connection establishment.
Anything that is wrong here or missing ?
Yes. it's being done. I create the engine and then set convert unicode =
True.
On 8/15/07, Michael Bayer [EMAIL PROTECTED] wrote:
are you using convert_unicode=True and/or the Unicode type ?
On Aug 15, 2007, at 12:01 PM, Arun Kumar PG wrote:
All tables are having a charset of utf8.
Any other clue that may be helpful in troubleshooting the cause ?
On 8/15/07, Arun Kumar PG [EMAIL PROTECTED] wrote:
Yes. it's being done. I create the engine and then set convert unicode =
True.
On 8/15/07, Michael Bayer [EMAIL PROTECTED] wrote:
are you using convert_unicode=True
Hi,
I have two questions:
1) what exact versions of MySQL (i.e. 4.1.22) and py-mysqldb?
2) how many databases and/or tables (an encodings) used in your
application?
On Aug 15, 9:57 pm, Arun Kumar PG [EMAIL PROTECTED] wrote:
Any other clue that may be helpful in troubleshooting the cause
So to recap, you are setting the character set on the dbapi
connection via the MySQLdb method in addition to issuing a manual
SET NAMES query?
Arun wrote:
Any other clue that may be helpful in troubleshooting the cause ?
On 8/15/07, Arun Kumar PG [EMAIL PROTECTED] wrote:
Yes. it's
I am using mysqldb-1.2.2. I am passing 'SET NAMES' to connect method as a
value for init_command parameter. All tables have utf8 charset. And I pass
convert_unicode=True to engine.
Let me know if anything else is required.
thanks!
On 8/15/07, jason kirtland [EMAIL PROTECTED] wrote:
So to
Ok you need to get tArun wrote:
I am using mysqldb-1.2.2. I am passing 'SET NAMES' to connect
method as a value for init_command parameter. All tables have
utf8 charset. And I pass convert_unicode=True to engine.
Let me know if anything else is required.
Ok, you need to get that charset to
16 matches
Mail list logo