so in your app, you can do this for now to monkeypatch the problem away:
engine.dialect.do_begin = lambda *arg, **kw: pass
the current steps in do_begin() are probably needed for savepoint
support, though I might try myself at the pycon sprints to isolate
exactly why, and if so we'd have to regulate that operation based on
some kind of engine flag (most likely enable_savepoint=True, something
like that).
On Mar 24, 2009, at 8:09 PM, davidlmontgomery wrote:
>
> The relevant change is the addition of the
> MSSQLDialect.do_begin method:
>
> def do_begin(self, connection):
> cursor = connection.cursor()
> cursor.execute("SET IMPLICIT_TRANSACTIONS OFF")
> cursor.execute("BEGIN TRANSACTION")
>
> This was first introduced three months ago
> to correct the savepoint tests
> http://bitbucket.org/mirror/sqlalchemy/changeset/985925326dc8/
>
> and revised a couple months ago to use the
> cursor rather than the connection:
> http://www.sqlalchemy.org/trac/browser/sqlalchemy/trunk/lib/sqlalchemy/databases/mssql.py?rev=5641
>
> With this method converted to a pass, 0.5.2 works
> properly for me on the three machines where before
> it always rolled back.
>
> David
>
> >
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"sqlalchemy" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/sqlalchemy?hl=en
-~----------~----~----~----~------~----~------~--~---
