Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: neutral (asf.osuosl.org: local policy)
Message-ID: <436BA88E.1020903@debrunners.com>
Date: Fri, 04 Nov 2005 10:29:34 -0800
From: Daniel John Debrunner <djd@debrunners.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.7.3) Gecko/20040910
MIME-Version: 1.0
To: derby-dev@db.apache.org
Subject: Re: [jira] Updated: (DERBY-231) "FOR UPDATE" required for updatable
 result set to work
References: <1423548905.1113999264585.JavaMail.jira@ajax.apache.org>
 <1821373379.1130947796422.JavaMail.jira@ajax.apache.org>
 <20051103001306.GB5919@barbar.sun.com> <436951E6.7000701@debrunners.com>
 <436A1825.2000708@sun.com> <436A5A76.2000706@debrunners.com>
 <20051103223528.GA6087@barbar.sun.com> <436AD2E6.9070108@debrunners.com>
 <20051104091550.GB21210@atum01.norway.sun.com>
In-Reply-To: <20051104091550.GB21210@atum01.norway.sun.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Bernt M. Johnsen wrote:


> Thus when you in JDBC writes
> 
> PreparedStatement p = c.prepareStatement("SELECT * FROM T");
> ResultSet rs = p.executeQuery();
> 
> it is equivalent to
> 
> PreparedStatement p = c.prepareStatement("SELECT * FROM T", 
>                                          ResultSet.TYPE_FORWARD_ONLY,
>                                          ResultSet.CONCUR_READ_ONLY);
> ResultSet rs = p.executeQuery();
> 
> which again should be equivalent something like
> 
> PREPARE p FROM SELECT * FROM T FOR READ ONLY;
> DECLARE rs NO SCROLL CURSOR FOR p;

That's the leap of faith I have trouble with. The assumption that the
read only of the result set means read only status of the SQL query.

I see the ResultSet.CONCUR_READ_ONLY only applying to the client side
ResultSet, because that's what it is declared to mean.

public static final int CONCUR_READ_ONLY

    The constant indicating the concurrency mode for a ResultSet object
that may NOT be updated.

And we have instances where we know the ResultSet being read only does
not make the SQL query read only, when the select includes the FOR UPDATE.

Dan.