db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Van Couvering <David.Vancouver...@Sun.COM>
Subject Re: [jira] Commented: (DERBY-243) connection toString should uniquely identify the connection
Date Tue, 24 May 2005 23:09:44 GMT
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...



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:,,,
>> 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.

View raw message