Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Development" <derby-dev@db.apache.org>
Received-SPF: neutral (hermes.apache.org: local policy)
Message-ID: <429F2F0A.50307@debrunners.com>
Date: Thu, 02 Jun 2005 09:08:42 -0700
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 Development <derby-dev@db.apache.org>
Subject: Re: Implementing Statement.cancel()
References: <427648FF.9010007@sun.com> <42765F37.7070201@debrunners.com>
 <428C9E5A.3060307@sun.com>
In-Reply-To: <428C9E5A.3060307@sun.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Oyvind.Bakksjo@sun.com wrote:

> Daniel John Debrunner wrote:
> 
>> Oyvind.Bakksjo@Sun.COM wrote:
>>
>>
>>> I've been looking at implementing Statement.cancel(), and later,
>>> Statement.setQueryTimeout().
>>
>>
>>
>> So, quick summary, that method is not suitable for finding the correct
>> StatementContext from EmbedStatement.cancel().
>>
>> I'll look into how I think you should track down the StatementContext.
>> Dan.
> 
> 
> Hi Dan,
> 
> have you had any time to look into this?
Not a lot :-(

I've been thinking about it and there are a couple of issues:

1) StatementContexts are created dynamically for the current running
statement

2) Derby does not keep references to application JDBC objects below the
JDBC layer. This is to ensure when any JDBC object (e.g. Statement)
moves out of scope for the application, it will be garbage collected and
lead to its closure.

I wonder if from a StatementContext you can determine the activation
because that would provide the link to the Statement.


Dan.