Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for autonomous transactions [CORE1409] #1827

Closed
firebird-issue-importer opened this issue Aug 8, 2007 · 14 comments
Closed

Support for autonomous transactions [CORE1409] #1827

firebird-issue-importer opened this issue Aug 8, 2007 · 14 comments

Comments

@firebird-issue-importer
Copy link

@firebird-issue-importer firebird-issue-importer commented Aug 8, 2007

Submitted by: Igor Lobov (ivl)

Is related to QA302

Votes: 1

To add support of autonomous transactions.

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Aug 8, 2007

Modified by: @asfernandes

assignee: Adriano dos Santos Fernandes [ asfernandes ]

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Aug 8, 2007

Commented by: Roman Rokytskyy (rrokytskyy)

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.

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Aug 8, 2007

Commented by: @asfernandes

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.

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Nov 8, 2007

Commented by: @asfernandes

Syntax:

IN AUTONOMOUS TRANSACTION DO <statement>

Example:

IN AUTONOMOUS TRANSACTION DO
BEGIN
INSERT INTO T VALUES (CURRENT_TIMESTAMP);
END

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Nov 8, 2007

Modified by: @asfernandes

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

Fix Version: 2.5 Alpha 1 [ 10224 ]

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Jan 28, 2008

Modified by: @pcisar

Workflow: jira [ 12780 ] => Firebird [ 14876 ]

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Feb 25, 2008

Commented by: Jonas Jasas (jon)

This feature would be great, and useful! Hope it will be implemented one day.

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Feb 25, 2008

Commented by: @dyemanov

The ticket is resolved as you could see, so it is already implemented :-)

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Mar 22, 2008

Commented by: Alexander Tyutik (tut)

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...

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Mar 22, 2008

Commented by: @asfernandes

In the moment, no.

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

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented May 4, 2008

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Jul 30, 2008

Commented by: Sascha Michel (datiscum1)

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 ?

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Feb 23, 2011

Modified by: @pcisar

Link: This issue is related to QA302 [ QA302 ]

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Jun 23, 2011

Modified by: @pmakowski

status: Resolved [ 5 ] => Closed [ 6 ]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants