You are viewing a plain text version of this content. The canonical link for it is here.

Posted to derby-dev@db.apache.org by "David Van Couvering (JIRA)" <de...@db.apache.org> on 2005/05/24 02:46:52 UTC

[jira] Closed: (DERBY-311) Add connection id to StatementCache VTI

     [ http://issues.apache.org/jira/browse/DERBY-311?page=all ]
     
David Van Couvering closed DERBY-311:
-------------------------------------

    Resolution: Invalid

Upon further inspection it has become clear that statements in the statement cache are global to the current schema and not specific to a given connection.  Any connection can use a statement out of the cache.  This is a nice feature, but it also makes this item invalid, so I am closing it.

> Add connection id to StatementCache VTI
> ---------------------------------------
>
>          Key: DERBY-311
>          URL: http://issues.apache.org/jira/browse/DERBY-311
>      Project: Derby
>         Type: Sub-task
>   Components: Services
>     Versions: 10.1.0.0
>     Reporter: David Van Couvering
>     Priority: Minor

>
> Add a column showing the connection id of the connection associated with this statement.  This allows correlation of the output of Connection.toString(), allows you to scope statements by connection, etc.

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