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

TIMEOUT parameter for AUTONOMOUS TRANSACTIONs [CORE5466] #5736

Closed
firebird-automations opened this issue Jan 22, 2017 · 4 comments
Closed

TIMEOUT parameter for AUTONOMOUS TRANSACTIONs [CORE5466] #5736

firebird-automations opened this issue Jan 22, 2017 · 4 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: PizzaProgram Ltd. (szakilaci)

Jira_subtask_inward CORE985
Duplicates CORE4017

Manipulating data of an other database from a transaction is a great feature. Really great!
Although it lacks of an important aspect: how long should it run maximum, before it is rolling back automatically.

Parameter should be given in milliseconds (int64)... or DOUBLE (0.05 = 50ms)
-1 = infinite
0 = this feature is disabled
<x = there can be an auto-minimum inside the engine : if (t<50) then t:=50; // maybe 20ms is enough too, needs testing

@firebird-automations
Copy link
Collaborator Author

Modified by: PizzaProgram Ltd. (szakilaci)

description: Manipulating data of an other database from a transaction is a great feature. Really great!
Although it lacks of an important aspect: how long should it run maximum, before it is rolling back automatically.

Parameter should be given in milliseconds (int64).
-1 = infinite
0 = this feature is disabled
<x = there can be an auto-minimum inside the engine : if (t<50) then t:=50; // maybe 20ms is enough too, needs testing

=>

Manipulating data of an other database from a transaction is a great feature. Really great!
Although it lacks of an important aspect: how long should it run maximum, before it is rolling back automatically.

Parameter should be given in milliseconds (int64)... or DOUBLE (0.05 = 50ms)
-1 = infinite
0 = this feature is disabled
<x = there can be an auto-minimum inside the engine : if (t<50) then t:=50; // maybe 20ms is enough too, needs testing

@firebird-automations
Copy link
Collaborator Author

Modified by: @hvlad

Link: This issue duplicates CORE4017 [ CORE4017 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @hvlad

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

resolution: Duplicate [ 3 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment