Hi,

Dne 26.9.2012 10:57, mariuz napsal(a):

>
> This seems to be a design issue
>
> http://article.gmane.org/gmane.comp.db.firebird.python/166/

I see. In fact, this is a bug in FDB (already fixed few days ago in
private tree). The correct behavior for commit() and rollback() is to do
nothing when called on (yet) inactive transaction (like KDB). However,
(trans/transaction)_info still check for active transaction,
because they need transaction handle to perform the API call.

btw, calling savepoint() on inactive transaction will start it, because
there is no such a thing as isc_savepoint API call, and savepoint is
created via execute_immediate that starts transaction when needed.

The new FDB version 0.8.6 with many bug fixes, enhancements,
optimizations AND shining new documentation will be released soon,
hopefully next week.

best regards
Pavel Cisar
IBPhoenix