Issue Details (XML | Word | Printable)

Key: CORE-1409
Type: New Feature New Feature
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Adriano dos Santos Fernandes
Reporter: Igor Lobov
Votes: 1
Watchers: 1

If you were logged in you would be able to see more operations.
Firebird Core

Support for autonomous transactions

Created: 08/Aug/07 12:16 PM   Updated: 23/Jun/11 11:01 AM
Component/s: Engine
Affects Version/s: None
Fix Version/s: 2.5 Alpha 1

Issue Links:

 Description  « Hide
To add support of autonomous transactions.

 All   Comments   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Roman Rokytskyy added a comment - 08/Aug/07 01:00 PM
Please provide exact description of what the autonomous transactions are. We had already the case where autonomous transactions where just another name to savepoints, which are fully supported by Firebird.

Adriano dos Santos Fernandes added a comment - 08/Aug/07 01:09 PM
Autonomous transaction is when a procedure or trigger run in another (self open and close) transaction.
This is very desired feature to use with database triggers.

Adriano dos Santos Fernandes added a comment - 08/Nov/07 04:26 PM




Jonas Jasas added a comment - 25/Feb/08 09:10 AM
This feature would be great, and useful! Hope it will be implemented one day.

Dmitry Yemanov added a comment - 25/Feb/08 10:11 AM
The ticket is resolved as you could see, so it is already implemented :-)

Alexander Tyutik added a comment - 22/Mar/08 02:35 PM
Is it possible to set transaction parameters for autonomous transactions?
Few years ago i used similar feature in MS SQL server an remember that we used such possiblility for some tasks...

Adriano dos Santos Fernandes added a comment - 22/Mar/08 02:38 PM
In the moment, no.

The new transaction starts with the same isolation level of the existing one.

Sascha Michel added a comment - 30/Jul/08 05:50 AM
OK to set Transaction parameters makes sense !

I have the following problem:

Using an ReadOnly Transaction for long outstanding commit
and a Write transaction for the Datachange.
Now it can be possible that in an Trigger or used SP that is joined with the select statemant
an write must be done for insert a initiale row.

When we can say
IN AUTONOMOUS WRITE TRANSACTION It would be very useful for this concept of long read and short write transactions.
We using FIBplus and here it can greatly help.

Or is that conncept og long outstanding ReadOnly transactions obsolete ?