Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 10516 invoked from network); 25 Jun 2005 00:54:08 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 25 Jun 2005 00:54:08 -0000 Received: (qmail 21773 invoked by uid 500); 25 Jun 2005 00:54:07 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 21542 invoked by uid 500); 25 Jun 2005 00:54:06 -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 21529 invoked by uid 99); 25 Jun 2005 00:54:06 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 24 Jun 2005 17:54:06 -0700 X-ASF-Spam-Status: No, hits=0.1 required=10.0 tests=HTML_30_40,HTML_MESSAGE,HTML_TITLE_EMPTY X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [192.18.98.34] (HELO brmea-mail-3.sun.com) (192.18.98.34) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 24 Jun 2005 17:54:06 -0700 Received: from phys-bur-1 ([129.148.9.72]) by brmea-mail-3.sun.com (8.12.10/8.12.9) with ESMTP id j5P0s3w4014112 for ; Fri, 24 Jun 2005 18:54:03 -0600 (MDT) Received: from conversion-daemon.bur-mail1.east.sun.com by bur-mail1.east.sun.com (iPlanet Messaging Server 5.2 HotFix 1.24 (built Dec 19 2003)) id <0IIM00H017HRAS@bur-mail1.east.sun.com> (original mail from Lance.Andersen@Sun.COM) for derby-dev@db.apache.org; Fri, 24 Jun 2005 20:54:03 -0400 (EDT) Received: from [127.0.0.1] (vpn-129-150-64-64.East.Sun.COM [129.150.64.64]) by bur-mail1.east.sun.com (iPlanet Messaging Server 5.2 HotFix 1.24 (built Dec 19 2003)) with ESMTPA id <0IIM003SK7U11S@bur-mail1.east.sun.com> for derby-dev@db.apache.org; Fri, 24 Jun 2005 20:54:03 -0400 (EDT) Date: Fri, 24 Jun 2005 20:54:00 -0400 From: "Lance J. Andersen" Subject: Re: JDBC auto-commit semantics challenge In-reply-to: <42BC84E2.2080906@sbcglobal.net> To: Derby Development Message-id: <42BCAB28.8090505@sun.com> MIME-version: 1.0 Content-type: multipart/alternative; boundary="Boundary_(ID_Pabj3a3skSQtqAtjB22cwQ)" X-Accept-Language: en-us, en User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax) References: <1119563352.54046.ezmlm@db.apache.org> <42BC0C49.3030403@acadiau.ca> <42BC1B78.3020206@debrunners.com> <42BC84E2.2080906@sbcglobal.net> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N This is a multi-part message in MIME format. --Boundary_(ID_Pabj3a3skSQtqAtjB22cwQ) Content-type: text/plain; charset=us-ascii; format=flowed Content-transfer-encoding: 7BIT i have not had the bandwidth to follow this thread due to J1 and a few other fire drills. We have made changes to the spec and javadocs in JDBC 4 to clarify things in these areas. Please take a look and see if there is still something you feel needs clarified. Kathey Marsden wrote: >Daniel John Debrunner wrote: > > > >>I think you dropped the footnotes that you had in the pdf document. >>The note that talked about JDBC 3.0 spec did not mention output >>parameters for auto commit on callable statements. >> >>I would challenge that the text from JDBC 3.0 spec, section 10.1 is the >>definitive behaviour, not the javadoc of setAutoCommit. >> >> >> >> >> >So does that make that a bug in the setAutoCommit javadoc? Lance do >you have an opinon here? > > > > > --Boundary_(ID_Pabj3a3skSQtqAtjB22cwQ) Content-type: text/html; charset=us-ascii Content-transfer-encoding: 7BIT i have not had the bandwidth to follow this thread due to J1 and a few other fire drills.  We have made changes to the spec and javadocs in JDBC 4 to clarify things in these areas.  Please take a look and see if there is still something you feel needs clarified.



Kathey Marsden wrote:
Daniel John Debrunner wrote:

  
I think you dropped the footnotes that you had in the pdf document.
The note that talked about JDBC 3.0 spec did not mention output
parameters for auto commit on callable statements.

I would challenge that the text from JDBC 3.0 spec, section 10.1 is the
definitive behaviour, not the javadoc of setAutoCommit.

 

    
So  does that make that a bug in the setAutoCommit javadoc?  Lance do
you have an opinon here?



  
--Boundary_(ID_Pabj3a3skSQtqAtjB22cwQ)--