Kbase P28296: Why do 4GL clients obtain limbo table locks when SQL clients
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
7/10/2003 |
|
Status: Unverified
GOAL:
Why do 4GL clients obtain limbo table locks when SQL clients access the database?
FACT(s) (Environment):
Progress 9.x
FIX:
When SQL is running, SQL uses table locks to maintain requested isolation levels. Since 4GL and SQL can run simultaneously, when the SQL engine is running the 4GL engine must use the same locking protocol as SQL which is to maintain table locks. This allows the two to coexist and maintain the requested isolation.
Table locks have no recid associated with them. The fact that 4GL clients obtain table locks in limbo simply means that a lock release request was made while in a transaction and since the 4GL clients obtained IX locks they will not actually be released until the end of the transaction.