db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Van Couvering (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-243) connection toString should uniquely identify the connection
Date Mon, 23 May 2005 16:31:53 GMT
     [ http://issues.apache.org/jira/browse/DERBY-243?page=all ]

David Van Couvering updated DERBY-243:

    Attachment: DERBY-243.diff

I have attached the latest patch in response to Kathey's comments.  

I added comments to the Javadoc for the connection string semantics, and I removed 
the toString() code for the client side.  derbyall passes with the exception of 
parameterMapping and backupRestore, which others have noted are currently failing.

Output of 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/jdbcapi/dataSourcePermissions.java
M      java/testing/org/apache/derbyTesting/functionTests/tests/jdbcapi/checkDataSource.java
M      java/testing/org/apache/derbyTesting/functionTests/tests/derbynet/dataSourcePermissions_net_sed.properties
M      java/testing/org/apache/derbyTesting/functionTests/master/DerbyNet/dataSourcePermissions_net.out
M      java/testing/org/apache/derbyTesting/functionTests/master/dataSourcePermissions.out
M       java/testing/org/apache/derbyTesting/functionTests/master/DerbyNetClient/dataSourcePermissions_net.out
M      java/testing/org/apache/derbyTesting/functionTests/master/checkDataSource.out
M      java/testing/org/apache/derbyTesting/functionTests/master/checkDataSource30.out
M      java/testing/org/apache/derbyTesting/functionTests/util/TestUtil.java

> 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:,,,
>  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:
For more information on JIRA, see:

View raw message