pymssql/pymssql — pull request #134 by ramiro (2014-04-30 19:45:15+00:00)
Title: callproc requires nextset to be called before it returns results

I am creating a new issue that more correctly defines what someone stumbled upon with issue #98. That issue is a little confusing so I closed it and opened this one.

The problem is that `callproc` does not return resultsets for a stored proc, until you call `nextset`.

Results of an example program at https://gist.github.com/msabramo/6747703

```
(mysql.venv)vagrant@lucid64:~/dev/git-repos/pymssql$ python callproc_comparison.py
******************************************************************************
Test MySQLdb
******************************************************************************

first use cursor.execute with a proc that returns 0 rows and then 3 rows and print out the rows and get an empty set:
()
then call nextset and get the 3 rows:
(('Tom',), ('Dick',), ('Harry',))

now use cursor.callproc, get an empty set
()
then call nextset and get the 3 rows:
(('Tom',), ('Dick',), ('Harry',))

******************************************************************************
Test pymssql
******************************************************************************

first use cursor.execute with a proc that returns 0 rows and then 3 rows and print out the rows and get an empty set:
[]
then call nextset and get the 3 rows:
[(u'Tom',), (u'Dick',), (u'Harry',)]

now use cursor.callproc, get an empty set
[]
then call nextset and get the 3 rows:
[]
```

The bug is that `cursor.callproc` is not returning the 3 rows.

The fix is easy and I will post it shortly... Basically, it's just to call `nextset()` in `callproc`.