Subject Re: [firebird-php] Re: Proper transaction & deadlock handling
Hi Daniel.

The code I used was very similar to yours.

Your test for failure is:

if ( $qh === false )

In my case I was updating an existing record so I was just testing as:

if (!$qh)

Hence it may be worth double checking by logging the errmsg when it is not identical to false just to see if there is an error message/code.

My only other thought is that because you have two scripts running it is possibly the "other" script that experiences the deadlock and writes the deadlock warning message.

I seem to remember that when I was testing this I could reproduce and detect the deadlock every time in PHP, which should give some hope for your debugging unless something fundamental has broken.