From: Brad Allen <bradallen137@gmail.com>
Date: Thu, 11 Mar 2010 22:30:49 +0000 (-0600)
Subject: Now using pyodbc execution context once again (to pass the test involving insert... 
X-Git-Tag: rel_0_6beta2~59
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=4f89831f886b6c347870d44a54476856ff706ff8;p=thirdparty%2Fsqlalchemy%2Fsqlalchemy.git

Now using pyodbc execution context once again (to pass the test involving insert to trigger table)
---

diff --git a/lib/sqlalchemy/dialects/mssql/mxodbc.py b/lib/sqlalchemy/dialects/mssql/mxodbc.py
index b43831046c..bf14601b87 100644
--- a/lib/sqlalchemy/dialects/mssql/mxodbc.py
+++ b/lib/sqlalchemy/dialects/mssql/mxodbc.py
@@ -7,8 +7,15 @@ from sqlalchemy.dialects.mssql.pyodbc import MSExecutionContext_pyodbc
 from sqlalchemy.dialects.mssql.base import MSExecutionContext, MSDialect
 
 
-class MSExecutionContext_mxodbc(MSExecutionContext):
-    pass
+class MSExecutionContext_mxodbc(MSExecutionContext_pyodbc):
+    """
+    The pyodbc execution context is useful for enabling
+    SELECT SCOPE_IDENTITY in cases where OUTPUT clause
+    does not work (tables with insert triggers).
+    """
+    #todo - investigate whether the pyodbc execution context
+    #       is really only being used in cases where OUTPUT
+    #       won't work.
 
 class MSDialect_mxodbc(MxODBCConnector, MSDialect):