About:
The pymssql module provides access to MS SQL databases from Python scripts. It implements version 2.0 of the Python DB API.

Author:
Andrzej Kukula [contact developer]

Rating:	reset 1 2 3 4 5 6 7 8 9 10
(not rated)

Homepage:
http://pymssql.sourceforge.net/
Tar/GZ:
http://sourceforge.net/project/showfiles.php?group_id=40059
CVS tree (cvsweb):
http://pymssql.cvs.sourceforge.net/

Trove categories: [change]

[Development Status]		5 - Production/Stable
[Environment]		Console (Text Based)
[Intended Audience]		Developers
[License]		OSI Approved :: GNU General Public License (GPL), OSI Approved :: GNU Lesser General Public License (LGPL)
[Operating System]		MacOS X, Microsoft :: Windows, POSIX :: BSD, POSIX :: Linux, POSIX :: SunOS/Solaris
[Programming Language]		C, Python
[Topic]		Database, Database :: Front-Ends, Software Development :: Libraries :: Python Modules

Dependencies: [change]
FreeTDS 0.63 (required)
Python 2.4 (required)
[download links]

 Branches

Branch	Version	Last release	License	URLs
Default	0.8.0	25-Sep-2006	GNU Lesser General Public License (LGPL)

 Comments

[»] lastset()
by Andrew Athan - Jul 21st 2007 06:31:00

When using certain types of queries/stored procedures that use intermediate selects and one final select, it is possible to get multiple result sets even though only the last select is intended to return data. This is the case even though SQL Query Analyzer doesn't show the intermediate result. If you use connection.execute() followed by connection.fetchall() then you will be fetching one of the intermediate empty result sets and it will appear that pymssql is not working correctly. To fix this, use nextset() to get to the last result set before fetchall(). Or, add this lastset() function:

def lastset(self):
if self._result == None:
return 0
self.__resultpos = len(self._result) - 1
return 1

--
Andrew Athan

[reply] [top]