Subject | Is it possible to avoid update deadlocks in Firebird ? |
---|---|
Author | Boguslaw Brandys |
Post date | 2004-05-31T18:50:35Z |
Hello,
I have a few executable SP called one after another, which did some
computations and among them update some goods count like in stock or
inventory list in a simple way like this :
update Goods_In_Stock set Amount = Amount + :Increment
where Goods = :Goods
If deadlock occur I would like to simply do commit, however becouse those
SP are called one after another I must do a rollback always becouse
deadlock origin is not known (if I use commit there will be partialy
written changes from previous executable SP - is it true? )
I'm wondering if there is a solution to avoid update deadlocks with
Firebird with use of insert , delete , select, another table combination ?
--
Best Regards
Bogusław Brandys
I have a few executable SP called one after another, which did some
computations and among them update some goods count like in stock or
inventory list in a simple way like this :
update Goods_In_Stock set Amount = Amount + :Increment
where Goods = :Goods
If deadlock occur I would like to simply do commit, however becouse those
SP are called one after another I must do a rollback always becouse
deadlock origin is not known (if I use commit there will be partialy
written changes from previous executable SP - is it true? )
I'm wondering if there is a solution to avoid update deadlocks with
Firebird with use of insert , delete , select, another table combination ?
--
Best Regards
Bogusław Brandys