[Sqlalchemy-commits] sqlalchemy: Now using pyodbc execution context once again (to pa...

[<co...@sq...>]

details:   http://hg.sqlalchemy.org/sqlalchemy/sqlalchemy/rev/03f1d76f66ce
changeset: 6247:03f1d76f66ce
user:      bradallen <bra...@gm...>
date:      Thu Mar 11 16:30:49 2010 -0600
description:
Now using pyodbc execution context once again (to pass the test involving insert to trigger table)

diffstat:

 lib/sqlalchemy/dialects/mssql/mxodbc.py |  11 +++++++++--
 1 files changed, 9 insertions(+), 2 deletions(-)

diffs (21 lines):

diff -r f6b4fa087d51 -r 03f1d76f66ce lib/sqlalchemy/dialects/mssql/mxodbc.py
--- a/lib/sqlalchemy/dialects/mssql/mxodbc.py	Thu Mar 11 16:26:32 2010 -0600
+++ b/lib/sqlalchemy/dialects/mssql/mxodbc.py	Thu Mar 11 16:30:49 2010 -0600
@@ -7,8 +7,15 @@
 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):