Possibility to prevent SHARE-LOCKs - OpenEdge Development - Products Enhancements - Progress Community

 OpenEdge Development

Possibility to prevent SHARE-LOCKs

The problem:

An EXCLUSIVE-LOCK is sometimes downgraded to SHARE-LOCK after a transaction (a documented feature). This might lead to locking issues, especially when making the transaction inside a persistent procedure (user can not update a record because it is unintentionally being share-locked by another user). It is usually very hard work to find out, which transaction leaves the share-lock on. There is no use for SHARE-LOCK in our application. 

The suggestion:

Provide a way to prevent SHARE-LOCKs and always downgrade EXCLUSIVE-LOCKs to NO-LOCKs after transaction.

E.g., add a new startup parameter: -nosharelock

I realize that the parameter could potentially break some (poorly programmed) old code but this would still be better that the current situation. 

Comments