pymssql fetch functions return nothing, traces back to freetdx and 1.0.x incompatibility

[Thomas Ward]

This has been reported by myself upstream in Debian as well, however this was originally found and confirmed in Ubuntu by myself.

I have copied the Debian bug contents here in the interim, as it is the same issue.

Note that since this prevents getting any data out of the SQL query results, I am marking this bug as "High" here. I have confirmed this on Trusty systems, I intend to test on Xenial soon after I get an MSSQL server set up for testing.

Getting an upgraded version of the pymssql package into this would be MUCH better; this was fixed in PyMSSQL upstream version 2.0.1 at the least, and using the workaround I specify below provides temporary solutions; though, the workaround requires removing python-pymssql.

============

Debian Bug Contents:

Package: python-pymssql
Version: 1.0.2+dfsg-1
Severity: important
Tags: fixed-upstream

It has been observed by myself and others that pymssql version 1.0.2 has
some type of incompatibility with freetdx 0.91, such that in 1.0.x of
pymssql when you attempt to fetchone() from a cursor after query
execution, you get an object of None back.

This means that fetchone and fetchall are both broken and *anything*
relying on getting results will be unusable. I've chosen an Important
severity, but it's much more likely this needs 'grave' severity.

------

Looking around on the internet for this issue, it was found [1] that
getting an upgraded version of pymssql solves the problem completely,
and then returns results for fetchone or fetchall.

Please, as such, provide an updated version of python-pymssql, using at
least version 2.0.1 of the pymssql Python package, which includes fixes
for this problem.

End-user workaround is to remove the python-pymssql package, and use
'easy_install --upgrade pymssql' or similar to install and compile the
pymssql library from source (this necessitates installation of
freetdx-dev though).

------
Thomas

[1]:
http://stackoverflow.com/questions/18760286/pymssql-not-returning-result-data