Return-Path: Delivered-To: apmail-db-derby-user-archive@www.apache.org Received: (qmail 46000 invoked from network); 3 Nov 2004 17:11:03 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 3 Nov 2004 17:11:03 -0000 Received: (qmail 88398 invoked by uid 500); 3 Nov 2004 17:11:02 -0000 Delivered-To: apmail-db-derby-user-archive@db.apache.org Received: (qmail 88314 invoked by uid 500); 3 Nov 2004 17:11:01 -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 88293 invoked by uid 99); 3 Nov 2004 17:11:01 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FORGED_RCVD_HELO X-Spam-Check-By: apache.org Received-SPF: neutral (hermes.apache.org: local policy) Received: from [32.97.182.101] (HELO e1.ny.us.ibm.com) (32.97.182.101) by apache.org (qpsmtpd/0.28) with ESMTP; Wed, 03 Nov 2004 09:10:59 -0800 Received: from d01relay02.pok.ibm.com (d01relay02.pok.ibm.com [9.56.227.234]) by e1.ny.us.ibm.com (8.12.10/NS PXFA) with ESMTP id iA3HAtcr395624 for ; Wed, 3 Nov 2004 12:10:55 -0500 Received: from d01av02.pok.ibm.com (d01av02.pok.ibm.com [9.56.224.216]) by d01relay02.pok.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id iA3HAtgQ276334 for ; Wed, 3 Nov 2004 12:10:55 -0500 Received: from d01av02.pok.ibm.com (loopback [127.0.0.1]) by d01av02.pok.ibm.com (8.12.11/8.12.11) with ESMTP id iA3HAtBw023245 for ; Wed, 3 Nov 2004 12:10:55 -0500 Received: from Remulak.Net (sig-9-48-106-216.mts.ibm.com [9.48.106.216]) by d01av02.pok.ibm.com (8.12.11/8.12.11) with ESMTP id iA3HAsgP023202 for ; Wed, 3 Nov 2004 12:10:54 -0500 Message-ID: <418910D8.CE3951AA@Remulak.Net> Date: Wed, 03 Nov 2004 09:09:44 -0800 From: Mamta Satoor X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Derby Discussion Subject: Re: Problems in using an SQL Client References: <4f17b29304110302333c814f30@mail.gmail.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N My guess is that the Statement object is getting created with default resultset TYPE_FORWARD_ONLY. Is there a way to configure the client to create the Statement with TYPE_SCROLL_INSENSITIVE? Mamta Amit Rao wrote: > I have configured iSQL- Viewer and tried to connected to derby from > it.I created a schem,table and inserted values into it...but when i > run a simple select query i get the following error (on the console in > iSQL). > > [15:51:12] Exception Occured While Retrieving Query Results > [15:51:12] Runtime Exception::(com.ibm.db2.jcc.c.SqlException: This > method should only be called on ResultSet objects that are > scrollable(type TYPE_SCROLL_SENSITIVE or TYPE_SCROLL_INSENSITIVE)) > > On reading around on the manual i came across the following in the > reference manual for > java.sql.Connection under section Table 15. JDBC 2.0 Connection > Methods Supported > > Returns : Statement > Signature : createStatement( int > resultSetType, int resultSetConcurrency) > Implementation Notes : ResultSet.TYPE_FORWARD_ONLY and > ResultSet.TYPE_SCROLL_INSENSITIVE are the only scrolling types > supported. If you request TYPE_SCROLL_SENSITIVE, Derby issues an > SQLWarning and returns a TYPE_SCROLL_INSENSITIVE ResultSet. > > Any work-around for this??? > Please help > > Thanks, > Amit