Kbase 18797: Subtleties of the RELEASE Statement
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
03/05/1999 |
|
The following details a few subtleties that you should know when
using the RELEASE statement:
1) First of all, the RELEASE statement is intended to release a
'BUFFER', not locks on the record in it. Depending on the state
of the buffer, RELEASE can have several side effects (including
changes in the lock status).
2) If the record in the buffer has been updated or if it contains a
newly created record and the record has not yet been written to
the database, it will get written to the server. Index entries
may be created also (if they are needed).
3) If there is a lock on the record in the buffer and you are in a
transaction, the lock cannot be dropped yet. The server will be
notified so it will know to release the lock at the end of the
transaction.
4) If there is a share lock on the record in the buffer and you are
not in a transaction, the lock can be dropped.
5) Finally, the buffer contents are discarded after any of the
relevant situations above have been taken care of.