[freetds] FreeTDS not giving any results
marca at surveymonkey.com
Fri Sep 6 10:18:18 EDT 2013
I've seen a similar behavior when using pymssql 1.0.2 with newer versions
of FreeTDS. No rows seem to come back. I didn't look in depth at
diagnosing and debugging it though, because 2 things seem to work around
1. Use an older version of FreeTDS. E.g.: the one packaged with our Ubuntu
10 systems, which is 0.82-6build1. This is reasonable for production.
2. Use a newer version of pymssql -- e.g.: the pymssql 2.X versions
installed with pip or directly from the source -- I do this for
development because I happen to do a lot of maintenance work on pymssql.
Personally, I'd love to have more folks looking at pymssql 2.X, because
I've invested time in it, but that's my own bias. :-)
I am very curious about the incompatibility between newer FreeTDS and the
older pymssql, so I will be interested to see what you find out.
On 9/6/13 5:51 AM, "James Andrewartha" <jandrewartha at ccgs.wa.edu.au> wrote:
>On 6/09/13 5:05 PM, "James Andrewartha" <jandrewartha at ccgs.wa.edu.au>
>>I have a python script that uses pymssql 1.0.2, that in turn uses
>>FreeTDS 0.91, connecting to a MSSQL 2008 server. It used to work, but
>>now I don't get any results. The FreeTDS log (below) show the data is
>>received, but it's not processed for some reason. I did some code diving
>>and printf debugging, and dblib.c sets the results_state to empty
>>because of a TDS_COMPUTEFMT_RESULT (line 4698 in dbsqlok). Does anyone
>>know why this is happening?
>A few other things about that log - it's actually from the development
>tarball, and the data processed is exactly the first packet received - the
>log doesn't record any others, and the TCP window fills up so it's not
>pulling them out of the socket buffer either.
>Network & Projects Engineer
>Christ Church Grammar School
>Claremont, Western Australia
>Ph. (08) 9442 1757
>Mob. 0424 160 877
>FreeTDS mailing list
>FreeTDS at lists.ibiblio.org
More information about the FreeTDS