When a transaction locks a resource, it monopolizes that resource until commit or rollback occurs. For example, when an update is made to a locked resource (row or page), the automatic locking by HiRDB implements the exclusive mode, which does not allow referencing, adding, updating, or deletion by other transactions. Consequently, other transactions must wait until commit or rollback occurs before it becomes possible to access the row that is being updated. However, if UNTIL DISCONNECT is specified in the LOCK statement, the lock will remain in effect until a DISCONNECT statement is executed or until commit occurs after the table is deleted.