[
https://issues.apache.org/jira/browse/DERBY-2087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12472761
]
Kristian Waagan commented on DERBY-2087:
----------------------------------------
In my opinion, Dans issues are valid.
Thus I will have to write my own connection-handling for my test, but that
might in deed be the best approach.
Unless there is still a strong wish to add the new method(s), what else remains
to wrap up this Jira issue?
I'm a bit unsure if there are any more patches requiring review (the first
follow-up patch?).
> Clean up of a database server directory after running junit tests.
> ------------------------------------------------------------------
>
> Key: DERBY-2087
> URL: https://issues.apache.org/jira/browse/DERBY-2087
> Project: Derby
> Issue Type: Improvement
> Components: Test
> Affects Versions: 10.3.0.0
> Reporter: Julius Stroffek
> Assigned To: Julius Stroffek
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: d2087.diff, d2087.stat, d2087_round2.diff,
> d2087_round2.stat, d2087_round2_try2.diff, d2087_round2_try2.stat,
> d2087_try2.diff, d2087_try2.stat
>
>
> If I create a test using multiple connections using code like this
> DataSource ds1 = JDBCDataSource.getDataSource("FIRSTDB1");
> JDBCDataSource.setBeanProperty(ds1, "connectionAttributes",
> "create=true");
> Connection conn1 = ds1.getConnection();
> the files created on a server does not get cleaned.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
