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 Fri, 06 May 2005 22:20:05 GMT
     [ http://issues.apache.org/jira/browse/DERBY-243?page=all ]

David Van Couvering updated DERBY-243:

    Attachment: DERBY-243.diff

I am attaching the patch that should resolve this bug.  I added toString() to the
appropriate connection classes and updated the dataSourcePermissions.java and 
dataSourcePermissions_net.java tests to test toString().  I mostly just verify
that two connections do not have the same string and follow the expected 
pattern.  I had to "sed" out the actual connection ids in the output so we
could guarantee a pass even if the ids change.

Here is the output of svn status

M      java\engine\org\apache\derby\impl\jdbc\EmbedConnection.java
M      java\engine\org\apache\derby\jdbc\EmbedPooledConnection.java
M      java\engine\org\apache\derby\iapi\jdbc\BrokeredConnection.java
M      java\testing\org\apache\derbyTesting\functionTests\tests\jdbcapi\dataSour
A      java\testing\org\apache\derbyTesting\functionTests\tests\jdbcapi\dataSour
M      java\testing\org\apache\derbyTesting\functionTests\tests\jdbcapi\copyfile
M      java\testing\org\apache\derbyTesting\functionTests\tests\derbynet\dataSou
M      java\testing\org\apache\derbyTesting\functionTests\tests\derbynet\dataSou
M      java\testing\org\apache\derbyTesting\functionTests\master\DerbyNet\dataSo
M      java\testing\org\apache\derbyTesting\functionTests\master\dataSourcePermi
M      java\testing\org\apache\derbyTesting\functionTests\master\DerbyNetClient\
M      java\client\org\apache\derby\client\ClientPooledConnection.java
M      java\client\org\apache\derby\client\am\Connection.java
M      java\client\org\apache\derby\client\am\LogicalConnection.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