db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Van Couvering (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-412) Connection toString should show type information and the meaning of the identifier that it prints
Date Fri, 15 Jul 2005 21:00:24 GMT
     [ http://issues.apache.org/jira/browse/DERBY-412?page=all ]

David Van Couvering updated DERBY-412:
--------------------------------------

    Attachment: DERBY-412.diff

Attached is the patch to resolve this bug.  I adjusted the order of the fields to match the
output of the error log, otherwise it is as proposed for the vote.

derbyall passes with no failures

svn status output:
M      java/engine/org/apache/derby/impl/jdbc/EmbedConnection.java
M      java/engine/org/apache/derby/jdbc/EmbedPooledConnection.java



> 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.
> org.apache.derby.impl.jdbc.EmbedConnection@efd552 (SESSONID = 2)
> Ultimately this could be expanded to included other diagnostic information e.g
> org.apache.derby.impl.jdbc.EmbedConnection@efd552 (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


Mime
View raw message