You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Kristian Waagan (JIRA)" <ji...@apache.org> on 2010/07/20 12:57:50 UTC
[jira] Closed: (DERBY-2468) would be nice if traceFile=filename
connection attribute would be supported with ClientConnectionPoolDataSource
and ClientXADataSource
[ https://issues.apache.org/jira/browse/DERBY-2468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Waagan closed DERBY-2468.
----------------------------------
Resolution: Duplicate
See duplicate issue for details (like progress on backporting).
> would be nice if traceFile=filename connection attribute would be supported with ClientConnectionPoolDataSource and ClientXADataSource
> --------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2468
> URL: https://issues.apache.org/jira/browse/DERBY-2468
> Project: Derby
> Issue Type: Improvement
> Components: Network Client
> Affects Versions: 10.3.1.4
> Reporter: Myrna van Lunteren
> Assignee: Kristian Waagan
> Priority: Trivial
>
> The functionality of creating a tracefile for the output currently works with DriverManager connections, by using tracefile=<filename> as well as with all DataSources when using the setting ds.setTraceFile("<filename>"). However, using tracefile="filename" only works as a connection attribute with ClientDataSource, not with ClientConnectionPoolDataSource nor ClientXADataSource.
> For completeness' sake it would be nice if this were supported.
> See for a test of this functionality jdbcapi/checkDataSource.java.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.