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: pass (hermes.apache.org: local policy)
Date: Tue, 24 May 2005 16:09:44 -0700
From: David Van Couvering <David.Vancouvering@Sun.COM>
Subject: Re: [jira] Commented: (DERBY-243) connection toString should uniquely
 identify the connection
In-reply-to: <1955690727.1116958196863.JavaMail.jira@ajax.apache.org>
To: Derby Development <derby-dev@db.apache.org>
Reply-to: David.Vancouvering@Sun.COM
Message-id: <4293B438.4010906@Sun.COM>
MIME-version: 1.0
Content-type: text/plain; charset=UTF-8
Content-transfer-encoding: 7BIT
User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.4) Gecko/20041214
References: <1955690727.1116958196863.JavaMail.jira@ajax.apache.org>

Does anyone else have any comments on this?  Kathey, are you OK with
this change?  If so, you could hold off on the patch I submitted and
wait for a new one with these changes...

Thanks,

David

Daniel John Debrunner (JIRA) wrote:

>     [ http://issues.apache.org/jira/browse/DERBY-243?page=comments#action_66186 ]
>     
>Daniel John Debrunner commented on DERBY-243:
>---------------------------------------------
>
>David wrote
>  
>
>>For this reason, it makes much more sense to use the LanguageConnectionContext as the owner of a unique identification for the session.
>>    
>>
>
>I agree, the LCC is the "physical connection", thus having it define the unique identification matches the definition.
>
>  
>
>>connection toString should uniquely identify the connection
>>-----------------------------------------------------------
>>
>>         Key: DERBY-243
>>         URL: http://issues.apache.org/jira/browse/DERBY-243
>>     Project: Derby
>>        Type: Improvement
>>  Components: JDBC
>>    Reporter: Kathey Marsden
>>    Assignee: David Van Couvering
>>    Priority: Trivial
>>     Fix For: 10.0.2.1, 10.0.2.0, 10.0.2.2, 10.1.0.0
>> Attachments: DERBY-243.diff
>>
>>The toString() on the Derby connection doesn't print 
>>unique information.
>>for example  System.out.println(conn) prints:
>>EmbedConnection  in the case of derby embedded
>>It would be great if the toString() method for connections could be used to differentiate one connection from another.
>>    
>>
>
>  
>