[
https://issues.apache.org/jira/browse/DERBY-4524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12803900#action_12803900
]
Bryan Pendleton commented on DERBY-4524:
----------------------------------------
+1 to removing the tearDown and letting CleanDatabaseTestSetup handle the
cleanup. Thanks for cleaning this up!
> Incorrect DROP FUNCTION logic in AccessTest's tearDown() method
> ---------------------------------------------------------------
>
> Key: DERBY-4524
> URL: https://issues.apache.org/jira/browse/DERBY-4524
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.6.0.0
> Reporter: Knut Anders Hatlen
> Assignee: Knut Anders Hatlen
> Fix For: 10.6.0.0
>
> Attachments: removeTearDown.diff
>
>
> public void tearDown() throws Exception {
> Statement st = createStatement();
> super.tearDown();
> try {
> st.executeUpdate("DROP FUNCTION PADSTRING");
> } catch (SQLException e) {
> // never mind.
> }
> }
> The DROP FUNCTION statement always fails with "No current connection" because
> super.tearDown(), which is called between createStatement() and
> executeUpdate(), closes the connection.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
