Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Development" <derby-dev@db.apache.org>
Message-ID: <1269902691.1117859326058.JavaMail.jira@ajax.apache.org>
Date: Sat, 4 Jun 2005 06:28:46 +0200 (CEST)
From: "Samuel Andrew McIntyre (JIRA)" <derby-dev@db.apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (DERBY-291) Debug VTIs should refer to connection
 string
In-Reply-To: <1812056499.1116266886058.JavaMail.jira@ajax.apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/DERBY-291?page=all ]

Samuel Andrew McIntyre updated DERBY-291:
-----------------------------------------

    Fix Version: 10.2.0.0
                     (was: 10.1.0.0)
    Environment: 

> Debug VTIs should refer to connection string
> --------------------------------------------
>
>          Key: DERBY-291
>          URL: http://issues.apache.org/jira/browse/DERBY-291
>      Project: Derby
>         Type: Improvement
>   Components: Store
>     Versions: 10.0.2.2, 10.1.0.0
>     Reporter: David Van Couvering
>     Priority: Minor
>      Fix For: 10.2.0.0

>
> Now that the connection toString() provides a unique value, we should display this in VTIs that show data that that can be scoped by connections (such as locks, statement caches, etc.).  We should add a column to these VTIs called "connection" which displays the toString() value of the associated connection.  This will allow debuggers to correlate particular items in the VTI with particular connections.

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