I'll be more than happy to implement this one, but can
someone let me know whether transactions can be "switched
off" within Firebird/Interbase? I only know that you can
use "read committed" and "record versioning", but even then,
when someone updates, it still creates a transaction...
Please elaborate on the value of this request. For instance
why would you want to "switch off the transactions"? That
will help me figure out what I can do to help.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I think Pete meant that he would like to see something that
prevents Marathon from asking if the issued transaction
should be committed or not. Now when you enter a select or
insert statement and you execute it via F9 Marathon later
asks you *always* if the transaction should be committed,
even if you just issued a select statement. It's correct
from the developer POV because every statement is
encapsulated in a transaction, but from the users POV I
agree with Pete.
So I think we should only make it so that Marathon should
not pop up a dialog "Do you want to commit?" when the
statement issued was just a select.
Comments?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=152149
Hi,
what do you mean by "switching off transactions"?
Regards,
Tilo Muetze
Logged In: YES
user_id=405789
if I do a select query it pops up with do you want to roll back or commit .. I want it on commit always ...
Logged In: YES
user_id=152149
Oh I see, ok this sounds useful. I will look into this.
Logged In: YES
user_id=888889
I'll be more than happy to implement this one, but can
someone let me know whether transactions can be "switched
off" within Firebird/Interbase? I only know that you can
use "read committed" and "record versioning", but even then,
when someone updates, it still creates a transaction...
Please elaborate on the value of this request. For instance
why would you want to "switch off the transactions"? That
will help me figure out what I can do to help.
Logged In: YES
user_id=152149
I think Pete meant that he would like to see something that
prevents Marathon from asking if the issued transaction
should be committed or not. Now when you enter a select or
insert statement and you execute it via F9 Marathon later
asks you *always* if the transaction should be committed,
even if you just issued a select statement. It's correct
from the developer POV because every statement is
encapsulated in a transaction, but from the users POV I
agree with Pete.
So I think we should only make it so that Marathon should
not pop up a dialog "Do you want to commit?" when the
statement issued was just a select.
Comments?