Yep, same here.
..on my mssql 2005, I tried this query batch:
"""
set implicit_transactions on
go
select 'After implicit ON', @@trancount
exec sp_datatype_info
go
select 'After query w/implicit', @@trancount
begin transaction
go
select 'After BEGIN', @@trancount
"""
Here's the output:
--------------------- ----
After implicit ON 0
---------------------------- ----
After query w/implicit 1
---------------- ----
After BEGIN 2
Our support team also found that calling commit() after the connect also
> worked. I guess this will
> close the outer transaction.
It's a bit of a hack, but it sounds like a simple 2-cent solution. We could
issue something like:
IF @@TRANCOUNT > 0
COMMIT
on connection establishment.
Rick
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"sqlalchemy" group.
To post to this group, send email to sqlalchemy@googlegroups.com
To unsubscribe from this group, send email to
sqlalchemy+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/sqlalchemy?hl=en
-~----------~----~----~----~------~----~------~--~---
