sqlalchemy+mssql+python3 query encoding
up vote
0
down vote
favorite
I'm new to sqlalchemy and am working on a small code that fetches data from my company's MS SQL server.
For some reason, the following query returns None. Even though the same query statement works perfectly when typed in an MS SQL console(in pycharm/datagrip).
It seems the problem is caused by the Chinese characters ("南宁市") in the where clause. I can query without any problem as long as there is no special(Chinese) characters in the where clause.
I am wondering if there is a way to solve the issue? Your input will be greatly appreciated.
>>from sqlalchemy import create_engine
>>engine = create_engine(****, connect_args={'charset':'GBK'})
>>conn = engine.connect()
>>rsps = conn.execute("SELECT * FROM COMPINTRODUCTION WHERE CITY='南宁市'").fetchone()
>>rsps is None
True
Software environment:
Client OS: Windows 10
DB Server: Microsoft SQL Server 2008
DB Charset: cp936
sqlalchemy version: 1.2.13
pymssql version: 2.1.4
python version: 3.6 (Anaconda)
add a comment |
up vote
0
down vote
favorite
I'm new to sqlalchemy and am working on a small code that fetches data from my company's MS SQL server.
For some reason, the following query returns None. Even though the same query statement works perfectly when typed in an MS SQL console(in pycharm/datagrip).
It seems the problem is caused by the Chinese characters ("南宁市") in the where clause. I can query without any problem as long as there is no special(Chinese) characters in the where clause.
I am wondering if there is a way to solve the issue? Your input will be greatly appreciated.
>>from sqlalchemy import create_engine
>>engine = create_engine(****, connect_args={'charset':'GBK'})
>>conn = engine.connect()
>>rsps = conn.execute("SELECT * FROM COMPINTRODUCTION WHERE CITY='南宁市'").fetchone()
>>rsps is None
True
Software environment:
Client OS: Windows 10
DB Server: Microsoft SQL Server 2008
DB Charset: cp936
sqlalchemy version: 1.2.13
pymssql version: 2.1.4
python version: 3.6 (Anaconda)
stackoverflow.com/questions/16024041/…
– Mitch Wheat
Nov 25 at 1:12
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I'm new to sqlalchemy and am working on a small code that fetches data from my company's MS SQL server.
For some reason, the following query returns None. Even though the same query statement works perfectly when typed in an MS SQL console(in pycharm/datagrip).
It seems the problem is caused by the Chinese characters ("南宁市") in the where clause. I can query without any problem as long as there is no special(Chinese) characters in the where clause.
I am wondering if there is a way to solve the issue? Your input will be greatly appreciated.
>>from sqlalchemy import create_engine
>>engine = create_engine(****, connect_args={'charset':'GBK'})
>>conn = engine.connect()
>>rsps = conn.execute("SELECT * FROM COMPINTRODUCTION WHERE CITY='南宁市'").fetchone()
>>rsps is None
True
Software environment:
Client OS: Windows 10
DB Server: Microsoft SQL Server 2008
DB Charset: cp936
sqlalchemy version: 1.2.13
pymssql version: 2.1.4
python version: 3.6 (Anaconda)
I'm new to sqlalchemy and am working on a small code that fetches data from my company's MS SQL server.
For some reason, the following query returns None. Even though the same query statement works perfectly when typed in an MS SQL console(in pycharm/datagrip).
It seems the problem is caused by the Chinese characters ("南宁市") in the where clause. I can query without any problem as long as there is no special(Chinese) characters in the where clause.
I am wondering if there is a way to solve the issue? Your input will be greatly appreciated.
>>from sqlalchemy import create_engine
>>engine = create_engine(****, connect_args={'charset':'GBK'})
>>conn = engine.connect()
>>rsps = conn.execute("SELECT * FROM COMPINTRODUCTION WHERE CITY='南宁市'").fetchone()
>>rsps is None
True
Software environment:
Client OS: Windows 10
DB Server: Microsoft SQL Server 2008
DB Charset: cp936
sqlalchemy version: 1.2.13
pymssql version: 2.1.4
python version: 3.6 (Anaconda)
asked Nov 19 at 15:52
H. W.
1
1
stackoverflow.com/questions/16024041/…
– Mitch Wheat
Nov 25 at 1:12
add a comment |
stackoverflow.com/questions/16024041/…
– Mitch Wheat
Nov 25 at 1:12
stackoverflow.com/questions/16024041/…
– Mitch Wheat
Nov 25 at 1:12
stackoverflow.com/questions/16024041/…
– Mitch Wheat
Nov 25 at 1:12
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
It seems the problem is caused by pymssql. I switch to odbc and the problem is gone.
New contributor
H. W. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
It seems the problem is caused by pymssql. I switch to odbc and the problem is gone.
New contributor
H. W. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
up vote
0
down vote
It seems the problem is caused by pymssql. I switch to odbc and the problem is gone.
New contributor
H. W. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
up vote
0
down vote
up vote
0
down vote
It seems the problem is caused by pymssql. I switch to odbc and the problem is gone.
New contributor
H. W. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
It seems the problem is caused by pymssql. I switch to odbc and the problem is gone.
New contributor
H. W. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
H. W. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered Nov 25 at 0:41
H. W.
1
1
New contributor
H. W. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
H. W. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
H. W. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53378288%2fsqlalchemymssqlpython3-query-encoding%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
stackoverflow.com/questions/16024041/…
– Mitch Wheat
Nov 25 at 1:12