[ http://issues.apache.org/jira/browse/DERBY-243?page=all ]
David Van Couvering updated DERBY-243:
--------------------------------------
Attachment: DERBY-243.diff
Revised patch based on Oystein's most recent review.
Changes since previous patch:
- Cleared up extraneous spaces
- Used Integer.toString(int) rather than new Integer(int).toString()
- Restored original checkDataSource30.java, it is no longer part of this patch
- Fixed Javadoc for EmbedPooledConnection.toString()
derbyall passes with no errors
svn status:
M java/engine/org/apache/derby/impl/jdbc/EmbedConnection.java
M java/engine/org/apache/derby/iapi/jdbc/BrokeredConnection.java
M java/engine/org/apache/derby/jdbc/EmbedPooledConnection.java
M
java/testing/org/apache/derbyTesting/functionTests/tests/lang/miscerrors.sql
M
java/testing/org/apache/derbyTesting/functionTests/tests/jdbcapi/checkDataSource.java
M java/testing/org/apache/derbyTesting/functionTests/master/miscerrors.out
> 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
> Versions: 10.0.2.1, 10.0.2.2, 10.1.0.0, 10.0.2.0
> Reporter: Kathey Marsden
> Assignee: David Van Couvering
> Priority: Trivial
> Fix For: 10.1.0.0
> Attachments: DERBY-243.diff
>
> 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
