Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <14940510.1159583480632.JavaMail.root@brutus>
Date: Fri, 29 Sep 2006 19:31:20 -0700 (PDT)
From: "Laura Stewart (JIRA)" <derby-dev@db.apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (DERBY-1683) Developer guide doc for scope of locks
 is incorrect  for one case of repeatable read.
In-Reply-To: <205251.1155338354470.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/DERBY-1683?page=all ]

Laura Stewart updated DERBY-1683:
---------------------------------

    Attachment: derby1683.diff
                rdevconcepts8424.html

Updated the dev guide topic per this issue. 
I also added several index entries and 
reformatted the topic so that there are now
"sections" with titles, which will make it easier to read
and locate information.

> Developer guide doc for scope of locks is incorrect  for one case of repeatable read.
> -------------------------------------------------------------------------------------
>
>                 Key: DERBY-1683
>                 URL: http://issues.apache.org/jira/browse/DERBY-1683
>             Project: Derby
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions: 10.0.2.0, 10.0.2.1, 10.1.1.0, 10.2.1.5, 10.1.2.1, 10.1.3.0, 10.1.3.1
>            Reporter: Sunitha Kambhampati
>         Assigned To: Laura Stewart
>            Priority: Minor
>             Fix For: 10.2.2.0
>
>         Attachments: derby1683.diff, rdevconcepts8424.html
>
>
> http://db.apache.org/derby/docs/dev/devguide/rdevconcepts8424.html
> There is this section under single-row locks.
> -------------
> For TRANSACTION_READ_COMMITTED or TRANSACTION_REPEATABLE_READ isolation, Derby treats rows as cursors for SELECT statements. It locks rows only as the application steps through the rows in the result. The current row is locked.
> -------------
> The last statement above is not true for Repeatable read.  The last stmt needs to be changed to--
> For TRANSACTION_REPEATABLE_READ isolation, the locks are released at the end of the transaction. For TRANSACTION_READ_COMMITTED,  it locks rows only as the application steps through the rows in the result. The current row is locked. 

-- 
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