Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 31875 invoked from network); 2 Jul 2005 00:53:35 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 2 Jul 2005 00:53:35 -0000 Received: (qmail 91456 invoked by uid 500); 2 Jul 2005 00:53:34 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 91229 invoked by uid 500); 2 Jul 2005 00:53:34 -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: "Derby Development" Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 91216 invoked by uid 99); 2 Jul 2005 00:53:34 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 01 Jul 2005 17:53:34 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [32.97.110.129] (HELO e31.co.us.ibm.com) (32.97.110.129) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 01 Jul 2005 17:53:36 -0700 Received: from westrelay02.boulder.ibm.com (westrelay02.boulder.ibm.com [9.17.195.11]) by e31.co.us.ibm.com (8.12.10/8.12.9) with ESMTP id j620rU8D387290 for ; Fri, 1 Jul 2005 20:53:30 -0400 Received: from d03av01.boulder.ibm.com (d03av01.boulder.ibm.com [9.17.195.167]) by westrelay02.boulder.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id j620rUgq329168 for ; Fri, 1 Jul 2005 18:53:30 -0600 Received: from d03av01.boulder.ibm.com (loopback [127.0.0.1]) by d03av01.boulder.ibm.com (8.12.11/8.13.3) with ESMTP id j620rTQ2031162 for ; Fri, 1 Jul 2005 18:53:29 -0600 Received: from [127.0.0.1] (sig-9-48-115-201.mts.ibm.com [9.48.115.201]) by d03av01.boulder.ibm.com (8.12.11/8.12.11) with ESMTP id j620rSI8031152 for ; Fri, 1 Jul 2005 18:53:29 -0600 Message-ID: <42C5E588.2030007@debrunners.com> Date: Fri, 01 Jul 2005 17:53:28 -0700 From: Daniel John Debrunner User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20040910 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Derby Development Subject: Re: JDBC auto-commit semantics challenge References: <42BFEF39.9000002@acadiau.ca> <42C58348.90202@sun.com> <42C5DFA2.6050801@sbcglobal.net> In-Reply-To: <42C5DFA2.6050801@sbcglobal.net> X-Enigmail-Version: 0.90.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Kathey Marsden wrote: > Lance J. Andersen wrote: > > >>I am just getting back from J1 and I have a quite a few emails to wade >>through. If/when you hace a cycle, if you can summarize the issues >>outstanding, i can look at it and discuss with the EG. There are sooo >>many emails from derby-dev, it is going to take me quite some time to >>digest it all. >> > > Hi Lance, > > Yes, there is a lot of mail. At least this thread would be worth > reading in its entirety. The executive summary as Philip would put it > is that > > Regarding the spec, the biggest items resolve to me seem to me to be. > > - When is a result set closed and when should next return false vs > throw an exception? I think it is well defined when a result set is closed, I think it's more once it is closed, what should its methods do? Especially rs.next(), return false or throw an exception. At least, for Lance & the EG, I think we need a better question than "when is a result set closed'. Dan.