There have been other reports of this issue, all specific to pyodbc. It
doesn't appear to be an issue with SA, as other MSSQL DBAPI modules don't
exhibit the problem.
Please raise the issue on the pyodbc list, I'll work with you if needed to
help resolve it.
Yes it appears to be a pyodbc problem, which is a shame because it's
making debugging my project incredibly difficult (and I've had even
more problems with the other MS SQL libraries like pymssql).
The bug report is here:
I read through the pyodbc forum quickly, and it looks as though this issue,
first reported back in April, cannot be reproduced by the maintainer. Pick
up the forum thread entitled
http://sourceforge.net/forum/forum.php?thread_id=1942313forum_id=550700
pyodbc pops bad exception since
Done - I really hope we can get this fixed because sqlalchemy and
TurboGears is incredibly difficult to use with MS SQL Server at the
moment. I think I may be able to improve sqlalchemy if I can get the
errors propogating properly
Cheers
Jon
