Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 19293 invoked from network); 13 Jun 2007 15:41:54 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 13 Jun 2007 15:41:54 -0000 Received: (qmail 71459 invoked by uid 500); 13 Jun 2007 15:41:56 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 71432 invoked by uid 500); 13 Jun 2007 15:41:56 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 71421 invoked by uid 99); 13 Jun 2007 15:41:56 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Jun 2007 08:41:56 -0700 X-ASF-Spam-Status: No, hits=1.4 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (herse.apache.org: 32.97.182.141 is neither permitted nor denied by domain of qozinx@gmail.com) Received: from [32.97.182.141] (HELO e1.ny.us.ibm.com) (32.97.182.141) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Jun 2007 08:41:52 -0700 Received: from d01relay04.pok.ibm.com (d01relay04.pok.ibm.com [9.56.227.236]) by e1.ny.us.ibm.com (8.13.8/8.13.8) with ESMTP id l5DFfViq030517 for ; Wed, 13 Jun 2007 11:41:31 -0400 Received: from d01av01.pok.ibm.com (d01av01.pok.ibm.com [9.56.224.215]) by d01relay04.pok.ibm.com (8.13.8/8.13.8/NCO v8.3) with ESMTP id l5DFfUaT557378 for ; Wed, 13 Jun 2007 11:41:30 -0400 Received: from d01av01.pok.ibm.com (loopback [127.0.0.1]) by d01av01.pok.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id l5DFfUR8026909 for ; Wed, 13 Jun 2007 11:41:30 -0400 Received: from [127.0.0.1] (svl-arbrown.svl.ibm.com [9.30.38.148]) by d01av01.pok.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id l5DFfRte026352 for ; Wed, 13 Jun 2007 11:41:30 -0400 Message-ID: <46701026.70708@gmail.com> Date: Wed, 13 Jun 2007 08:41:26 -0700 From: Army User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.1) Gecko/20040707 X-Accept-Language: en-us, en MIME-Version: 1.0 To: derby-dev@db.apache.org Subject: Re: Updating rows with an open cursor...what is the expected behavior? References: <466ED7F4.407@gmail.com> <466EE859.4080400@sbcglobal.net> <466EEF36.5080801@gmail.com> <466FABB3.6050608@sun.com> <466FB135.7090209@sun.com> In-Reply-To: <466FB135.7090209@sun.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked by ClamAV on apache.org J�rgen L�land wrote: > I discussed this with Bernt just now, and found the following in the > JDBC 4 spec to be of interest as well: [ snip JDBC 4 quotes ] > It looks like the default behavior (TYPE_FORWARD_ONLY) is more or less > the same as SQL ASENSITIVE. "That is, it contains the rows that satisfy > the query ... as the rows are retrieved" should allow different results > when index and scan are used. Thank you *very* much for investigating this, J�rgen! Both of your emails were very helpful--and ultimately provided exactly the info that I was looking for. Many many thanks! Army