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

connection toString should uniquely identify the connection

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

Details

    • Improvement
    • Status: Closed
    • Trivial
    • Resolution: Fixed
    • 10.0.2.0, 10.0.2.1, 10.0.2.2, 10.1.1.0
    • 10.1.1.0
    • JDBC
    • None

    Description

      The toString() on the Derby connection doesn't print
      unique information.
      for example System.out.println(conn) prints:
      EmbedConnection in the case of derby embedded

      It would be great if the toString() method for connections could be used to differentiate one connection from another.

      Attachments

        Issue Links

        is depended upon by

        Improvement - An improvement or enhancement to an existing feature or task. DERBY-291 Debug VTIs should refer to connection string

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

        Improvement - An improvement or enhancement to an existing feature or task. DERBY-292 Add a Connection VTI

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

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

          People

            davidvc David Van Couvering
            kmarsden Katherine Marsden
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment