[ http://issues.apache.org/jira/browse/DERBY-243?page=all ]
Kathey Marsden updated DERBY-243:
---------------------------------
Summary: connection toString should uniquely identify the connection
(was: connection toString doesn't give enough information)
Description:
The toString() on the Derby connection doesn't print
unique information.
for example System.out.println(conn) prints:
EmbedConnection in the case of derby embedded
It would be great if the toString() method for connections could be used to
differentiate one connection from another.
was:
The toString() on the Derby connection doesn't print
unique information.
for example System.out.println(conn) prints:
EmbedConnection in the case of derby embedded
I am not sure if XA Connections and Pooled Connections have the same issue. I
didn't immediately see an override of the toString() method in
BrokeredConnection.java like there is for EmbedConnection
> connection toString should uniquely identify the connection
> -----------------------------------------------------------
>
> Key: DERBY-243
> URL: http://issues.apache.org/jira/browse/DERBY-243
> Project: Derby
> Type: Improvement
> Components: JDBC
> Reporter: Kathey Marsden
> Assignee: David Van Couvering
> Priority: Trivial
> Fix For: 10.0.2.1, 10.0.2.0, 10.0.2.2, 10.1.0.0
>
> The toString() on the Derby connection doesn't print
> unique information.
> for example System.out.println(conn) prints:
> EmbedConnection in the case of derby embedded
> It would be great if the toString() method for connections could be used to
> differentiate one connection from another.
--
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
