Subject | no-wait vs wait transactions? |
---|---|
Author | |
Post date | 2014-07-08T19:37:48Z |
Hi!
I have Firebird 2.x database which from time to time has rather long transactions - up to 30 seconds and so, there is high probability that the same record will be updated from the several different transactions and the lock conflict - deadlock exeption will be raised. I am currently using nowait transactions.
The question is - what is the best option in this case - to use wait or nowait transactions? My feeling is that it is better to invest in optimization and decreas of the running time and keep the nowait mode. Btw, who needs to have two or more transactions in queue.
The other problem with wait transactions can be the fact that database is used by several applications and not all of them will migrate from no-wait to wait transaction. Can this be an issue somehow?
Which is the best option in no-wait vs wait transactions and which option does emulate the BDE transaction behaviour most closely?
Thanks,
Jonatan
I have Firebird 2.x database which from time to time has rather long transactions - up to 30 seconds and so, there is high probability that the same record will be updated from the several different transactions and the lock conflict - deadlock exeption will be raised. I am currently using nowait transactions.
The question is - what is the best option in this case - to use wait or nowait transactions? My feeling is that it is better to invest in optimization and decreas of the running time and keep the nowait mode. Btw, who needs to have two or more transactions in queue.
The other problem with wait transactions can be the fact that database is used by several applications and not all of them will migrate from no-wait to wait transaction. Can this be an issue somehow?
Which is the best option in no-wait vs wait transactions and which option does emulate the BDE transaction behaviour most closely?
Thanks,
Jonatan