[ 
http://issues.apache.org/jira/browse/DERBY-412?page=comments#action_12316388 ] 

David Van Couvering commented on DERBY-412:
-------------------------------------------

Yes, you are right, the output doesn't match the agreed upon output.  I still 
have code in  BrokeredConnection that just prints out the toString() of the 
connection it wraps. 

Looking at this more closely, however, it is probably useful to know the class 
of the connection wrapped by BrokeredConnection.    And if we do that, I think 
it's important to provide a unique id for each BrokeredConnection instance

So instead of 

"[EMAIL PROTECTED] (XID = 19), (SESSIONID = 1), (DATABASE = wombat), (DRDAID = 
null) "

it should be

"[EMAIL PROTECTED] (ID=22), Wrapped Connection = [EMAIL PROTECTED] (XID = 19), 
(SESSIONID = 1), (DATABASE = wombat), (DRDAID = null) "

What do you think?

> Connection toString should show type information and  the meaning of the 
> identifier that it prints
> --------------------------------------------------------------------------------------------------
>
>          Key: DERBY-412
>          URL: http://issues.apache.org/jira/browse/DERBY-412
>      Project: Derby
>         Type: Bug
>     Versions: 10.1.1.0, 10.2.0.0
>     Reporter: Kathey Marsden
>     Assignee: David Van Couvering
>      Fix For: 10.2.0.0
>  Attachments: DERBY-412.diff
>
> After the change for DERBY-243 the  connection toString() output is  an 
> integer which correspond to SESSIONID.  The output should identify the type 
> and also the meaning of the identifier that it prints.  Perhaps a format that 
> appends the default toString output with the sessionid information as it 
> prints in the derby.log would be more informative.
> [EMAIL PROTECTED] (SESSONID = 2)
> Ultimately this could be expanded to included other diagnostic information e.g
> [EMAIL PROTECTED] (XID = 132), (SESSIONID = 5), (DATABASE = wombat), (DRDAID 
> = NF000001.H324-940125304405039114{7})

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

Reply via email to