nextset always returns true

[GoogleCodeExporter]

Using pymssql 1.0.2 on a Ubuntu machine.

To reproduce the problem you may use this code:

cursor = connection.cursor()
ret = cursor.execute("select 1")
while 1:
    if 0 == cursor.nextset():
        break
raise Exception("boom!")

Agains my expectation, the exception never geets thrown and the loop goes on 
forever.

Original issue reported on code.google.com by fcorr...@gmail.com on 7 Sep 2010 at 6:01

[GoogleCodeExporter]

I can't say for sure if this is the same issue, but it seems to be:
http://sourceforge.net/tracker/index.php?func=detail&aid=2886445&group_id=40059&
atid=426919

Any plans on releasing a 1.0.3 stable version before 2.0?

Original comment by fcorr...@gmail.com on 7 Sep 2010 at 6:39

[GoogleCodeExporter]

A workaround to this issue is simple not to use queries with multiple result 
sets...

Unfortunately, in the case I'm facing, this implies a 8x performance decrease :(
I'm currently using a variable table, and I then reuse it's data in several 
queries. To work around this issue I have changed my code to use a temporary 
table instead, which as expected, turns out to be much, much, slower.

Please tell me if you need any further test from my part on this issue.

Original comment by fcorr...@gmail.com on 8 Sep 2010 at 2:31

[GoogleCodeExporter]

I've just tried with pymssql 1.9.908 and it works. Is this version stable or is 
it just an intermediate (and unstable) step towards 2.0?

Original comment by fcorr...@gmail.com on 8 Sep 2010 at 2:59

[GoogleCodeExporter]

The following commit is the one that solves this issue:
http://pymssql.cvs.sourceforge.net/viewvc/pymssql/pymssql/mssqldbmodule.c?r1=1.4
0&r2=1.41

Btw, it would really be nice to have a 1.0.3 version, while version 2.0 isn't 
final...

Original comment by fcorr...@gmail.com on 17 Sep 2010 at 6:33

[GoogleCodeExporter]

This issue as been submitted as a bug report to Red Hat's Bugzilla: 
https://bugzilla.redhat.com/show_bug.cgi?id=635223

Original comment by fcorr...@gmail.com on 18 Sep 2010 at 10:46

[GoogleCodeExporter]

I think there may be 1.0.3 soon.

Original comment by akuk...@gmail.com on 21 Sep 2010 at 2:03

• Changed state: Started

[GoogleCodeExporter]

@akukula eagerly waiting for it :) thanks!

Original comment by fcorr...@gmail.com on 21 Sep 2010 at 10:18

[GoogleCodeExporter]

Hello akukula! Any progress on this?
Please let me know if i can help in any way.

Original comment by fcorr...@gmail.com on 4 Jan 2011 at 1:54

[GoogleCodeExporter]

Sorry I can't continue work on pymssql now and I'm unable to say if and when 
this will change. If you have necessary skills, you can join pymssql 
development.

Original comment by akuk...@gmail.com on 4 Jan 2011 at 3:02

[GoogleCodeExporter]

I will quite likely release a 1.9.909 version soon as I have finally managed to 
get the latest snapshot of FreeTDS built on Windows. This version has quite a 
lot of changes from 1.9.908 currently.

Original comment by dam...@gmail.com on 4 Jan 2011 at 8:52

[GoogleCodeExporter]

Original comment by dam...@gmail.com on 8 Mar 2011 at 3:37

• Added labels: PyMssql-1.x

[GoogleCodeExporter]

Sounds like this was fixed in tip, not going to do anything else with 1.x 
branch.

Original comment by rsyr...@gmail.com on 8 Mar 2012 at 3:08

• Changed state: WontFix

[GoogleCodeExporter]

Linux distributions won't move to any version considered unstable, otherwise I 
would be happy to move to 2.x. So, in the current state of things, I still 
think it could be worth doing a release from the old branch (1.3?). There are a 
few bugs (this one included) that are fixed there, but that that were never 
released as a stable version.

Original comment by fcorr...@gmail.com on 8 Mar 2012 at 3:15