Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: pass (asf.osuosl.org: local policy)
Date: Mon, 06 Mar 2006 12:24:21 +0100
From: Fernanda Pizzorno <Fernanda.Pizzorno@Sun.COM>
Subject: Re: Subject: Detectability of updates in DRDA
In-reply-to: <440B79DB.10302@amberpoint.com>
To: derby-dev@db.apache.org
Message-id: <440C1BE5.60206@sun.com>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7BIT
User-Agent: Mozilla Thunderbird 1.0.7 (X11/20050930)
References: <4408630D.5070900@sun.com> <440B79DB.10302@amberpoint.com>

Bryan Pendleton wrote:

>> For updates, is is not exactly what we want, since we do not intend to
>> requalify a row after it has been updated (thereby possibly making it
>> an "update hole").
>
>
> Would it be possible for you to expand on this? I've read through your
> message several times, and I've also read through Appendix B of DRDA V.1
> several times, and I'm still struggling to understand the details here.
>
> If you could perhaps just give a short example of a table with a couple
> rows, and a cursor which has this problem, so that I can understand
> this better, I'd be most grateful.
>
> thanks,
>
> bryan
>
>
We want to scrollable insensitive updatable result sets to be able to
detect own updates. So the JDBC ResultSet.rowUpdated() method should
return true if the row has been visibly updated by the owner or
someone else.

If we have the following result set:

ID    Name
--    ------------------
1     Fernanda

we update the name:

ID    Name
--    ------------------
1     Fernanda Pizzorno

if we later call the rowUpdated() method while positioned on the updated
row, this method should return true.

What we are looking for is a mechanism that we can use to implement the
ResultSet#rowUpdated() method.

Fernanda