db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] Created: (DERBY-3431) DatabaseMetaData.getConnection returns the wrong connection when using connection pooling
Date Tue, 19 Feb 2008 10:12:43 GMT
DatabaseMetaData.getConnection returns the wrong connection when using connection pooling
-----------------------------------------------------------------------------------------

                 Key: DERBY-3431
                 URL: https://issues.apache.org/jira/browse/DERBY-3431
             Project: Derby
          Issue Type: Bug
          Components: JDBC, Network Client
    Affects Versions: 10.4.0.0
         Environment: Client-server with connection pooling enabled.
            Reporter: Kristian Waagan
            Priority: Minor


The connection returned from DatabaseMetaData.getConnection is not the same as the connection
used to create the meta data object when the client driver is used with connection pooling
enabled.
For trunk, the embedded driver/ds does the right thing.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message