Closed GoogleCodeExporter closed 8 years ago
Original comment by mkleehammer
on 18 Dec 2011 at 6:54
This appears to be fixed in 3.0.x. If you run the tests2/freetdstests.py unit
tests, you'll see one named test_varchar_upperlatin that is equivalent. (I
also changed the character to 236 to match your test exactly and that worked
also.)
Original comment by mkleehammer
on 18 Dec 2011 at 7:03
Hi,
I am facing a similar problem, using pyodbc '3.0.6'
the database is reporting character iso_1 and collation Modern_Spanish_CI_AS
using isql I get the correct results, using pyodbc, I get ? where I sould be gettin ñ or accentuated vowels,
best regards,
Alberto
Original comment by alberto....@gmail.com
on 17 Oct 2012 at 3:50
python: 2.6.5 (r265:79063, Oct 1 2012, 22:04:36)
[GCC 4.4.3]
pyodbc: 3.0.7-beta10 /usr/src/pyodbc/build/lib.linux-x86_64-2.6/pyodbc.so
odbc: 03.52
driver: libtdsodbc.so 0.82
supports ODBC version 03.00
os: Linux
unicode: Py_Unicode=4 SQLWCHAR=2
server: MSSQL-2000, Cyrillic_General_BIN
tests2/freetdstests.py fails 36 tests with unicode, text, varchar, etc
Original comment by qwigly...@gmail.com
on 11 Dec 2012 at 12:05
SQL_WCHAR is not supported by 0.82
http://lists.ibiblio.org/pipermail/freetds/2010q1/025572.html
Original comment by qwigly...@gmail.com
on 11 Dec 2012 at 5:11
Original issue reported on code.google.com by
enricose...@hotmail.com
on 3 Nov 2011 at 9:07