Subject | commit rollback retaining savepoints |
---|---|
Author | Philippe Makowski |
Post date | 2011-07-11T16:54:11Z |
Hi,
I start looking at the pyfirebirdsql code and the sqlalchemy dialect
sqlalchemy use commit and rollback retain (it is bad IMHO and should be
change)
Werner I will ask you to test this change soon (still with kinterbasdb)
I just need to setup a public mercurial repository for that
but this lead me to see that kinterbasdb have commit(retaining=False)
and rollback(retaining=False)
so we need the same for pyfirebirdsql and also Connection.savepoint(name)
see doc :
http://web.firebirdsql.org/devel/python/docs/3.3.0/beyond-python-db-api.html#advanced-transaction-control
and
http://web.firebirdsql.org/devel/python/docs/3.3.0/python-db-api-compliance.html#nominally-supported-optional-features
can someone can help me with that ?
it will help me to understand better the code, all that is really new
for me, and I'm not a Python expert, but this will help me to improve my
skills I hope
thanks
I start looking at the pyfirebirdsql code and the sqlalchemy dialect
sqlalchemy use commit and rollback retain (it is bad IMHO and should be
change)
Werner I will ask you to test this change soon (still with kinterbasdb)
I just need to setup a public mercurial repository for that
but this lead me to see that kinterbasdb have commit(retaining=False)
and rollback(retaining=False)
so we need the same for pyfirebirdsql and also Connection.savepoint(name)
see doc :
http://web.firebirdsql.org/devel/python/docs/3.3.0/beyond-python-db-api.html#advanced-transaction-control
and
http://web.firebirdsql.org/devel/python/docs/3.3.0/python-db-api-compliance.html#nominally-supported-optional-features
can someone can help me with that ?
it will help me to understand better the code, all that is really new
for me, and I'm not a Python expert, but this will help me to improve my
skills I hope
thanks