| Subject | RE: [firebird-support] Deadlock |
|---|---|
| Author | |
| Post date | 2014-03-17T14:45:55Z |
I think you are correct on the 'lock conflict'. After posting the original message, I started reviewing the error log and noticed several 'lock conflict on No Wait transaction'. This would make sense as this is a key part of the security and this procedure is called on every read/write to the database
That raises three questions:
1) Should I put a WAIT in the procedure with a LOCK TIMEOUT?
2) Would it be better to a START TRANSACTION / COMMIT inside the procedure as opposed to putting the transaction control in the FbClient?
1) Should I put a WAIT in the procedure with a LOCK TIMEOUT?
2) Would it be better to a START TRANSACTION / COMMIT inside the procedure as opposed to putting the transaction control in the FbClient?
3) If I put it in the FbClient, what are the options I should choose? Would it be better to put it on the FbCommand or the FbConnection
Dixon