Return-Path: Delivered-To: apmail-db-derby-user-archive@www.apache.org Received: (qmail 37303 invoked from network); 26 Apr 2005 14:54:37 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 26 Apr 2005 14:54:37 -0000 Received: (qmail 41441 invoked by uid 500); 26 Apr 2005 14:54:14 -0000 Delivered-To: apmail-db-derby-user-archive@db.apache.org Received: (qmail 41387 invoked by uid 500); 26 Apr 2005 14:54:14 -0000 Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Reply-To: "Derby Discussion" Delivered-To: mailing list derby-user@db.apache.org Received: (qmail 41360 invoked by uid 99); 26 Apr 2005 14:54:14 -0000 X-ASF-Spam-Status: No, hits=0.2 required=10.0 tests=RCVD_BY_IP,UPPERCASE_25_50 X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: domain of msatoor@gmail.com designates 64.233.184.196 as permitted sender) Received: from wproxy.gmail.com (HELO wproxy.gmail.com) (64.233.184.196) by apache.org (qpsmtpd/0.28) with ESMTP; Tue, 26 Apr 2005 07:54:13 -0700 Received: by wproxy.gmail.com with SMTP id 58so1803833wri for ; Tue, 26 Apr 2005 07:53:14 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=DgBCFxLycJCJJQfAwU9mLx9rRRXsEdG3u7vfc7fpFA2FJIqHg2sEgmpp7tIUxfZFNEDGsPr/ES3Xv5ENLymSk9pJlgpXnUmgMhouWjoSbJZii38g6vlxEvSff3F4hrobhZJVBiI2lCNln72UBjtGvkx+F/7mxCJxIQ65w+FSDx8= Received: by 10.54.43.6 with SMTP id q6mr2593712wrq; Tue, 26 Apr 2005 07:53:14 -0700 (PDT) Received: by 10.54.49.63 with HTTP; Tue, 26 Apr 2005 07:53:14 -0700 (PDT) Message-ID: Date: Tue, 26 Apr 2005 07:53:14 -0700 From: Mamta Satoor Reply-To: Mamta Satoor To: Derby Discussion , Dag.Wanvik@sun.com Subject: Re: Features? Status? In-Reply-To: <17006.12030.506707.826151@sun.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <17006.12030.506707.826151@sun.com> X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Hi, Yes, Derby supports all the srollable methods on a scroll insensitive resultset type. Mamta On 4/26/05, Dag H. Wanvik wrote: >=20 > Hi Peter, >=20 > > Which ResultSet types does derby support (TYPE_FORWARD_ONLY, > > TYPE_SCROLL_INSENSITIVE, TYPE_SCROLL_SENSITIVE)? >=20 > I just looked at this and it seems this is the present state: >=20 > FORWARD_ONLY SCROLLABLE_INSENSITIVE SCROLLABLE_SENSITI= VE > -------------------------------------------------------------= -- > READ_ONLY | OK OK No > UPDATABLE | in working [Not allowed in SQL-99] No > Update | DERBY-99 > Delete | DERBY-98 > Insert | DERBY-100 >=20 > Patches for JIRA issues DERBY-99 and DERBY-98 are included on head of > the development trunk. Over on the dev list, there is a proposal to > start looking at adding support for updatable, scrollable result sets > (sensitive). >=20 > > Are all the methods for scrolling supported (previous(), afterLast(), > > getRow() etc.)? >=20 > As for the methods, my impression is "yes", but I didn't look at that > in detail yet, maybe someone else can confirm it? >=20 > Thanks, >=20 > Dag >