| Subject | Re: [firebird-support] Lock Conflict deadLock ... |
|---|---|
| Author | Helen Borrie |
| Post date | 2005-02-25T13:19:19Z |
At 09:55 AM 25/02/2005 -0300, you wrote:
merely indicate that one transaction tried to update the same row (or rows)
that another transaction also is updating. They are perfectly normal
occurrences.
The "repair" (if any) is to add appropriate code to your application, to
detect these exceptions and handle them - usually by rolling back the
transaction, or by re-trying the failing request.
./heLen
>HI,These errors are NOT a sign that the database is in need of repair. They
>
>I had a problem with my Database and among the messages of mistake
>that show is : lock Clonflict and deadlock.
>
>Which is the Better way to repair of the Database.
merely indicate that one transaction tried to update the same row (or rows)
that another transaction also is updating. They are perfectly normal
occurrences.
The "repair" (if any) is to add appropriate code to your application, to
detect these exceptions and handle them - usually by rolling back the
transaction, or by re-trying the failing request.
./heLen