derby documentation does not reflect changes to update lock behavior
--------------------------------------------------------------------
Key: DERBY-678
URL: http://issues.apache.org/jira/browse/DERBY-678
Project: Derby
Type: Bug
Components: Documentation
Versions: 10.0.2.0
Reporter: Mike Matrigali
Fix For: 10.2.0.0
The following section in the developers guide on update locks needs to be
changed from:
When a user-defined update cursor (created with the FOR UPDATE clause) reads
data, its transaction obtains an update lock on the data. If the user-defined
update cursor updates the data, the update lock is converted to an exclusive
lock. If the cursor does not update the row, when the transaction steps through
to the next row, transactions using the TRANSACTION_READ_COMMITTED isolation
level release the lock, and transactions using the TRANSACTION_SERIALIZABLE or
TRANSACTION_REPEATABLE_READ isolation level downgrade it to a shared lock until
the transaction is committed. (For update locks, the
TRANSACTION_READ_UNCOMMITTED isolation level acts the same way as
TRANSACTION_READ_COMMITTED.)
to:
When a user-defined update cursor (created with the FOR UPDATE clause) reads
data, its transaction obtains an update lock on the data. If the user-defined
update cursor updates the data, the update lock is converted to an exclusive
lock. If the cursor does not update the row, when the transaction steps through
to the next row, transactions using the TRANSACTION_READ_COMMITTED isolation
level release the lock.
(For update locks, the TRANSACTION_READ_UNCOMMITTED isolation level acts the
same way as TRANSACTION_READ_COMMITTED.)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
