Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 94146 invoked from network); 26 May 2005 13:00:52 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 26 May 2005 13:00:52 -0000 Received: (qmail 32030 invoked by uid 500); 26 May 2005 13:00:51 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 31990 invoked by uid 500); 26 May 2005 13:00:50 -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 31974 invoked by uid 99); 26 May 2005 13:00:50 -0000 X-ASF-Spam-Status: No, hits=0.2 required=10.0 tests=NO_REAL_NAME X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy) Received: from brmea-mail-4.Sun.COM (HELO brmea-mail-4.sun.com) (192.18.98.36) by apache.org (qpsmtpd/0.28) with ESMTP; Thu, 26 May 2005 06:00:48 -0700 Received: from phys-epost-1 ([129.159.136.14]) by brmea-mail-4.sun.com (8.12.10/8.12.9) with ESMTP id j4QD0e0R010222 for ; Thu, 26 May 2005 07:00:41 -0600 (MDT) Received: from conversion-daemon.epost-mail1.sweden.sun.com by epost-mail1.sweden.sun.com (iPlanet Messaging Server 5.2 HotFix 1.24 (built Dec 19 2003)) id <0IH300L01KLGO8@epost-mail1.sweden.sun.com> (original mail from Oyvind.Bakksjo@Sun.COM) for derby-dev@db.apache.org; Thu, 26 May 2005 15:00:40 +0200 (MEST) Received: from [129.159.112.222] (atum22.Norway.Sun.COM [129.159.112.222]) by epost-mail1.sweden.sun.com (iPlanet Messaging Server 5.2 HotFix 1.24 (built Dec 19 2003)) with ESMTPA id <0IH300G6NLH4IE@epost-mail1.sweden.sun.com> for derby-dev@db.apache.org; Thu, 26 May 2005 15:00:40 +0200 (MEST) Date: Thu, 26 May 2005 15:00:40 +0200 From: Oyvind.Bakksjo@Sun.COM Subject: DERBY-31: More on semantics for Statement.setQueryTimeout: ResultSet.updateRow To: Derby Development Message-id: <4295C878.8070709@sun.com> Organization: Sun Microsystems MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 8BIT X-Accept-Language: en, no, ru User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040618 X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Previously, we agreed that the query timeout should apply to Statement.execute() as well as each individual call to ResultSet.next(). New question: Should the query timeout apply to ResultSet.updateRow() as well. For orthogonality, the question (although this is more of theoretical interest) also applies to ResultSet.deleteRow()? My initial gut feeling is that it should not; even though updating e.g. a large blob may take a while, I still think timing out on an operation like this would be more annoying than useful to the user. -- �yvind Bakksj� Sun Microsystems, Web Services, Database Technology Group Haakon VII gt. 7b, N-7485 Trondheim, Norway Tel: x43419 / +47 73842119, Fax: +47 73842101