Skip to content

Conversation

ramiro
Copy link
Contributor

@ramiro ramiro commented Apr 29, 2014

This allows calling any of the fetch*() methods after a SP call to
capture a result set of a query performed by it, just like it's already
possible by iterating over the connection object.

This allows calling any of the fetch*() methods after a SP call to
capture a result set of a query performed by it, just like it's already
possible by iterating over the connection object.
@ramiro
Copy link
Contributor Author

ramiro commented Apr 29, 2014

@msabramo @damoxc @rsyring Opinions welcome.

@ramiro
Copy link
Contributor Author

ramiro commented Apr 29, 2014

Could be related to #134.

@ramiro
Copy link
Contributor Author

ramiro commented Apr 30, 2014

Looking at #134 I see this issue is strongly related to it.

Calling pymssql's cursor .nextset() as discussed on that issue among other things sets cursor .description.

Because of this I'm closing this as a duplicate.

@ramiro ramiro closed this Apr 30, 2014
@ramiro ramiro deleted the allow-calling-fetch-methods-after-sp-call branch October 25, 2014 22:09
@termim termim mentioned this pull request Oct 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant