Failure to pass Unicode characters to callproc; failing test: tests.test_sprocs.TestCallProcFancy.testCallProcWithUnicodeStringWithRussianCharacters about pymssql

[GoogleCodeExporter]

I'm sorry, I don't.  I do know that when I ran through the SQLAlchemy test 
suite with pymssql, I had some unicode related tests fail.  I can do the 
byte/unicode dance at the python level, but dropping down into cython & 
freetds, I'm pretty lost.

Original comment by [email protected] on 15 Jan 2013 at 2:59

[GoogleCodeExporter]

Original comment by [email protected] on 27 Feb 2013 at 6:45

• Changed title: Failure to pass Unicode characters to callproc; failing test: tests.test_sprocs.TestCallProcFancy.testCallProcWithUnicodeStringWithRussianCharacters

[GoogleCodeExporter]

This can be reproduced with:

tox -e py27 -- -v 
tests.test_sprocs:TestCallProcFancy.testCallProcWithUnicodeStringWithRussianChar
acters

Original comment by [email protected] on 27 Feb 2013 at 6:53

[GoogleCodeExporter]

This appears to be due to an issue in FreeTDS that has already been fixed in 
the [FreeTDS git repo](http://gitorious.org/freetds/freetds).

See http://lists.ibiblio.org/pipermail/freetds/2013q1/028272.html

Original comment by [email protected] on 5 Mar 2013 at 12:19

[GoogleCodeExporter]

With a recent version of FreeTDS from git 
(a11092a21fc9ba5996854244c573248ef208e04f) installed on my OS X 10.8.2 system, 
all of the stored proc tests pass:

tox -e py27 -- -s -v tests.test_sprocs
...
tests.test_sprocs.TestCallProcFancy.testCallProcWithAsciiString ... ok
tests.test_sprocs.TestCallProcFancy.testCallProcWithNone ... ok
tests.test_sprocs.TestCallProcFancy.testCallProcWithUnicodeStringWithNoFunnyChar
acters ... ok
tests.test_sprocs.TestCallProcFancy.testCallProcWithUnicodeStringWithRussianChar
acters ... ok
tests.test_sprocs.TestCallProcFancy.testExecuteWithAsciiString ... ok
tests.test_sprocs.TestCallProcFancy.testExecuteWithNone ... ok
tests.test_sprocs.TestCallProcFancy.testExecuteWithUnicodeStringWithNoFunnyChara
cters ... ok
tests.test_sprocs.TestCallProcFancy.testExecuteWithUnicodeWithRussianCharacters
... ok
tests.test_sprocs.TestFixedTypeConversion.testBigInt ... ok
tests.test_sprocs.TestFixedTypeConversion.testBit ... ok
tests.test_sprocs.TestFixedTypeConversion.testDateTime ... ok
tests.test_sprocs.TestFixedTypeConversion.testDecimal ... SKIP
tests.test_sprocs.TestFixedTypeConversion.testInt ... ok
tests.test_sprocs.TestFixedTypeConversion.testMoney ... ok
tests.test_sprocs.TestFixedTypeConversion.testNumeric ... SKIP
tests.test_sprocs.TestFixedTypeConversion.testSmallInt ... ok
tests.test_sprocs.TestFixedTypeConversion.testTinyInt ... ok
tests.test_sprocs.TestStringTypeConversion.testChar ... ok
tests.test_sprocs.TestStringTypeConversion.testText ... ok
tests.test_sprocs.TestStringTypeConversion.testVarChar ... ok

---

Ran 20 tests in 0.392s

OK (SKIP=2)

Original comment by [email protected] on 5 Mar 2013 at 12:26

[GoogleCodeExporter]

Change 
http://code.google.com/p/pymssql/source/detail?r=d053412736735062ebe009ad4ec34f8
fbaab0025

makes it skip this test since it's not a bug in pymssql; it's dependent on the 
version of FreeTDS installed.

Original comment by [email protected] on 5 Mar 2013 at 12:37

• Changed state: Fixed

[GoogleCodeExporter]

I'm not sure I'd skip the test.  Rather, we should build pymssql with the 
FreeTDS that works.  That is one of the reasons I liked the idea of bundling 
our own FreeTDS, we wouldn't need to worry about version compatibility, we 
could just use what works.

Original comment by [email protected] on 5 Mar 2013 at 2:23