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, 16 May 2005 17:57:11 GMT
     [ http://issues.apache.org/jira/browse/DERBY-243?page=all ]

David Van Couvering updated DERBY-243:

    Attachment: DERBY-243.diff

I have replaced the old patch with this one.  This one uses UUID to identify a connection
It also provides independent connection strings for PooledConnection classes.  

I also added some new tests to jdbcapi/checkDataSource and jdbcapi/CheckDataSource30.  I refactored
the code to ensure two toStrings() are not unique for two separate objects and put this
into TestUtil.

All tests pass, except for tools/dblook_test.java, which has a single-line diff that looks
unrelated.  I am investigating and may report a separate bug on this.

Here is svn status output:

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/dataSour
M      java/testing/org/apache/derbyTesting/functionTests/tests/jdbcapi/checkDat
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/testing/org/apache/derbyTesting/functionTests/master/checkDataSource
M      java/testing/org/apache/derbyTesting/functionTests/master/checkDataSource
M      java/testing/org/apache/derbyTesting/functionTests/suites/derbyall.proper
M      java/testing/org/apache/derbyTesting/functionTests/util/TestUtil.java
M      java/client/org/apache/derby/client/ClientPooledConnection.java
M      java/client/org/apache/derby/client/am/Connection.java
A      java/client/org/apache/derby/client/am/BasicUUID.java
A      java/client/org/apache/derby/client/am/BasicUUIDFactory.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