[Sqlalchemy-commits] sqlalchemy: using executemany instead of executedirect, which pa...

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

details:   http://hg.sqlalchemy.org/sqlalchemy/sqlalchemy/rev/771487e8714e
changeset: 6251:771487e8714e
user:      bradallen <bra...@gm...>
date:      Mon Mar 15 11:39:03 2010 -0600
description:
using executemany instead of executedirect, which passes more tests than with plain execute. Later we need to define logic to determine when to call the normal execute.

diffstat:

 lib/sqlalchemy/connectors/mxodbc.py |  8 +++-----
 1 files changed, 3 insertions(+), 5 deletions(-)

diffs (24 lines):

diff -r 27224a50b8ad -r 771487e8714e lib/sqlalchemy/connectors/mxodbc.py
--- a/lib/sqlalchemy/connectors/mxodbc.py	Mon Mar 15 11:01:50 2010 -0600
+++ b/lib/sqlalchemy/connectors/mxodbc.py	Mon Mar 15 11:39:03 2010 -0600
@@ -82,11 +82,8 @@
         return tuple(version)
     
     def do_execute(self, cursor, statement, parameters, context=None):
-        # temporary hack to pass tests until the a better solution is understood
-        try:
-            cursor.execute(statement, tuple(parameters))
-        except InterfaceError:
-            cursor.executedirect(statement, tuple(parameters))
+        cursor.executedirect(statement, tuple(parameters))
+
 
             
 def error_handler(connection, cursor, errorclass, errorvalue):
@@ -99,5 +96,6 @@
                   category=errorclass,
                   stacklevel=2)
     else:
+        #import pdb; pdb.set_trace()
         raise errorclass, errorvalue