The problem with mssql.py and adodbapi is that mssql.py assumes that adodbapi is using auto-commit and disables all the commit logic! In my case, the DB is not auto-committing so nothing ever gets committed.
adodbapi has code in it to do the right thing depending on whether transactions are enabled in the DB but the code to detect the DB setting is broken, maybe that is why transactions were turned off in mssql. It looks like correct operation of mssql with adodbapi requires a patched adodbapi, at least to get support for client cursors (for autoload to work) and correct transaction support. The adodbapi project itself is dormant. There was some discussion last October on the Python db-sig list about taking over maintenance but it doesn't seem to have gone anywhere. I'll ask over there to see if anything has happened. I'm not sure how to proceed here; include a patched adodbapi with SA? Assume that transactions *are* available? Put a correct test for transaction support in mssql? Any ideas? Kent ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Sqlalchemy-users mailing list Sqlalchemy-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users
