[
https://issues.apache.org/jira/browse/DERBY-3431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Waagan updated DERBY-3431:
-----------------------------------
Attachment: derby-3431-3b-client_logical_metadata.diff
'derby-3431-3b-client_logical_metadata.diff' addresses the comments Knut Anders
made, and contains a few other minor changes.
-- StatementPoolingTests
Extended test to check for implementation class, to make sure a JDBC 4 class
is returned in a JDBC 4 env.
-- Reference to the real metadata object
There is no reference to the real / physical metadata object anymore. The
getMetaData method of the physical connection is called each time the object
needs to be accessed.
-- LogicalDatabaseMetaData.getRealMetaDataObject
I was a bit lazy and didn't want to remove the method, as it would probably
require that many lines would become longer than 80 characters... Can be
removed (make logicalCon protected / package-private then).
The regression tests passed, but I made a few late changes so I'm running them
again. Will report back when they're done.
Patch ready for another round of review.
> 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.1.3.1, 10.2.2.0, 10.3.2.1, 10.4.1.3, 10.5.0.0
> Environment: Client-server with connection pooling enabled.
> Reporter: Kristian Waagan
> Assignee: Kristian Waagan
> Priority: Minor
> Fix For: 10.5.0.0
>
> Attachments: derby-3431-1a-test_repro.diff,
> derby-3431-1b-test_repro.diff, derby-3431-2a-test.diff,
> derby-3431-3a-client_logical_metadata.diff,
> derby-3431-3a-client_logical_metadata.stat,
> derby-3431-3b-client_logical_metadata.diff
>
>
> 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.
