From 4f89831f886b6c347870d44a54476856ff706ff8 Mon Sep 17 00:00:00 2001 From: Brad Allen Date: Thu, 11 Mar 2010 16:30:49 -0600 Subject: [PATCH] Now using pyodbc execution context once again (to pass the test involving insert to trigger table) --- lib/sqlalchemy/dialects/mssql/mxodbc.py | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) 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): -- 2.47.3