Wrong handling of failures of TRANSACTION START trigger
-------------------------------------------------------
Key: CORE-5843
URL: http://tracker.firebirdsql.org/browse/CORE-5843
Project: Firebird Core
Issue Type: Bug
Components: Engine
Affects Versions: 4.0 Alpha 1
Reporter: Vlad Khorsun
There are two general cases when TRANSACTION START trigger is fired
1. when user start transaction, and
2. when IN AUTONOMOUS TRANSACTION statement starts new transaction.
Let look what happens if TRANSACTION START is present and raises error.
According to documentation (see README.db_triggers.txt):
- TRANSACTION START
Triggers are fired in the newly user created transaction - uncaught
exceptions are returned to the client and the transaction is rolled-back.
In the 1st case new transaction is not rolled-back currently and left active
until Firebird process alive.
In the 2nd case new transaction is rolled-back but it also fires TRANSACTION
ROLLBACK trigger
which is wrong. Note, in the 1st case TRANSACTION ROLLBACK trigger is not fired.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://tracker.firebirdsql.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
