Uploaded image for project: 'Derby'
  1. Derby
  2. DERBY-5718

UniqueConstraintSetNullTest calls super.tearDown() too early

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 10.9.1.0
    • 10.9.1.0
    • Test
    • None

    Description

      UniqueConstraintSetNullTest calls super.tearDown() first in its tearDown() method. After that, it opens a new connection and does some more cleanup. This connection is not closed or nulled out. If super.tearDown() had been called last, it would have been cleaned up correctly.

      Attachments

        Issue Links

        blocks

        Improvement - An improvement or enhancement to an existing feature or task. DERBY-5726 Make it more difficult to forget calling super.tearDown() from BaseJDBCTestCase's subclasses

        • Minor - Minor loss of function, or other problem where easy workaround is present.
        • Closed

        Activity
          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            knutanders Knut Anders Hatlen
            knutanders Knut Anders Hatlen
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment