Return-Path: 
 <derby-dev-return-6720-apmail-db-derby-dev-archive=db.apache.org@db.apache.org>
Delivered-To: apmail-db-derby-dev-archive@www.apache.org
Received: (qmail 87205 invoked from network); 12 Jul 2005 18:22:31 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 12 Jul 2005 18:22:31 -0000
Received: (qmail 64876 invoked by uid 500); 12 Jul 2005 18:22:27 -0000
Delivered-To: apmail-db-derby-dev-archive@db.apache.org
Received: (qmail 64845 invoked by uid 500); 12 Jul 2005 18:22:27 -0000
Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:derby-dev-help@db.apache.org>
list-unsubscribe: <mailto:derby-dev-unsubscribe@db.apache.org>
List-Post: <mailto:derby-dev@db.apache.org>
List-Id: <derby-dev.db.apache.org>
Reply-To: "Derby Development" <derby-dev@db.apache.org>
Delivered-To: mailing list derby-dev@db.apache.org
Received: (qmail 64831 invoked by uid 99); 12 Jul 2005 18:22:27 -0000
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=SPF_FAIL
X-Spam-Check-By: apache.org
Received: from [192.87.106.226] (HELO ajax.apache.org) (192.87.106.226)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Jul 2005 11:22:14 -0700
Received: from ajax.apache.org (ajax.apache.org [127.0.0.1])
	by ajax.apache.org (Postfix) with ESMTP id DED5517
	for <derby-dev@db.apache.org>; Tue, 12 Jul 2005 20:22:11 +0200 (CEST)
Message-ID: <815731577.1121192531911.JavaMail.jira@ajax.apache.org>
Date: Tue, 12 Jul 2005 20:22:11 +0200 (CEST)
From: "David Van Couvering (JIRA)" <derby-dev@db.apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-412) Connection toString should show type
 information and  the meaning of the identifier that it prints
In-Reply-To: <475708805.1120082337381.JavaMail.jira@ajax.apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

    [ 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 connections.  

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

>
> 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