Subject | sqlalchemy ticket 2125 |
---|---|
Author | Philippe Makowski |
Post date | 2011-07-08T07:32:57Z |
Hi,
I'll try to work on the ticket:
http://www.sqlalchemy.org/trac/ticket/2125
I'm not a sqlalchemy user, but I know well Firebird and I'm helping to
support the pyfirebirdslq driver for Firebird
I have one question about the kinterbasdb dialect inside sqlalchemy :
I saw that you are using commit and rollback retain
is there any good reason for that ?
from the Firebird point of vue, it is not a very good way to work with
transaction
is that only because after a commit or rollback sqlalchemy need a
transaction handle ? or is there any other reason for this choice ?
thanks
--
Philippe Makowski
http://www.ibphoenix.com
Supporting users of Firebird
Tel +33 (0) 561058813
I'll try to work on the ticket:
http://www.sqlalchemy.org/trac/ticket/2125
I'm not a sqlalchemy user, but I know well Firebird and I'm helping to
support the pyfirebirdslq driver for Firebird
I have one question about the kinterbasdb dialect inside sqlalchemy :
I saw that you are using commit and rollback retain
is there any good reason for that ?
from the Firebird point of vue, it is not a very good way to work with
transaction
is that only because after a commit or rollback sqlalchemy need a
transaction handle ? or is there any other reason for this choice ?
thanks
--
Philippe Makowski
http://www.ibphoenix.com
Supporting users of Firebird
Tel +33 (0) 561058813