|
|
|||||||||
|
|||||||||
| |||||||||
|
|
|
| |||||||||
![]() |
|
|
«
Previous Thread
|
Next Thread
»
|
Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
#1
|
|||
|
|||
|
Firebird major problem
I've discovered a Firebird's major problem, and i don't know how to solve it.
I have two apps updating the same record using transactions. If one app has a connection failure and didn't get the chance to commit, the other app hangs, waiting for the other app to commit, but that will never gonna happen, until you do a restart of the firebird server. If anybody knows a method on how to solve this problem, without the "dummy packet" option because that is not a safe one, i appreciate. Thanks. |
|
#2
|
||||
|
||||
|
Can't you use the method suggested in firebird.conf?
Quote:
__________________
My blog about OpenSource Databases PDF tutorials about OSS databases, DBMonster ... Please contribute to Open Source Development, fill bug reports!!! Developer Shed eSupport Commented my.ini/my.cnf (PLEASE ADD YOUR OWN CONFIG TRICK) An introduction to database normalization Natural or Surrogate key Custom ordering for your results Correlated and uncorrelated subqueries Don't turn your outer joins into inner joins |
|
#3
|
|||
|
|||
|
Quote:
I wouldn't use that option because it has a big warning, and i don't know about the effects it has on the operating system (reducing it from 2 hours to 1 minute). |
|
#4
|
||||
|
||||
|
The warning says not to use the dummy packet interval option and suggests the workarounds I reported in my previous post.
|
![]() |
| Viewing: Dev Shed Forums > Databases > Firebird SQL Development > Firebird major problem |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|
|
|