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] Commented: (DERBY-412) Connection toString should show type information and the meaning of the identifier that it prints
Date Tue, 12 Jul 2005 18:22:11 GMT
    [ http://issues.apache.org/jira/browse/DERBY-412?page=comments#action_12315613 ] 

David Van Couvering commented on DERBY-412:

I am planning on using the following format for connection strings.  This addresses only embedded

A separate JIRA item (DERBY-293) addresses network client connections.

For some background on the different types of connections in Derby, see the comments for DERBY-243

Here are the message strings I am proposing:

Physical Connections, Pooled Connections (EmbedConnection, EmbedConnection30,
 BrokeredConnection, BrokeredConnection30):
    <classname>@<hashcode> (DATABASE=<dbname>), (SESSID=<sessid>),
(DRDAID=<drdaid>), (TXID=<txid>)

Pooled Connections (EmbedPooledConnection, EmbedXAConnection):
    <classname>@<hashcode> (ID=<uniqueid>), Physical Connection=<underlying
connection string>

Comments are most welcome

> 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:,
>     Reporter: Kathey Marsden
>     Assignee: David Van Couvering
>      Fix For:

> 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:
For more information on JIRA, see:

View raw message