db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kathey Marsden <kmarsdende...@sbcglobal.net>
Subject Re: [jira] Updated: (DERBY-243) connection toString should uniquely identify the connection
Date Thu, 12 May 2005 21:58:09 GMT
David Van Couvering wrote:

>> Connection.toString() is  a pretty quick and dirty debugging
>> technique. If you call toString() to debug your connections  it would
>> be nice if the output made it obvious what it meant without going to
>> a manual.  
> The output is pretty straightforward, it tells you it is a connection
> and then prints out the UUID.  Here is an example:
> Connection c013800d-0103-d219-2006-ffffe2f84f9d
I think I finally found in one of the old mails what I was looking for
which was what this represents.

David wrote ..

>>In summary, each physical connection should have its own unique
>> connection id, regardless of how it is obtained by the application.

Dan wrote ...

>That's a good definition. And it means the nested connection would need
>to have same toString() value as its parent.

So maybe  something like:
Physical Connection c013800d-0103-d219-2006-ffffe2f84f9d

Would be clearer


View raw message