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

Debug VTIs should refer to connection string

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Open
    • Minor
    • Resolution: Unresolved
    • 10.0.2.2, 10.1.1.0
    • None
    • Store
    • None
    • Low

    Description

      Now that the connection toString() provides a unique value, we should display this in VTIs that show data that that can be scoped by connections (such as locks, statement caches, etc.). We should add a column to these VTIs called "connection" which displays the toString() value of the associated connection. This will allow debuggers to correlate particular items in the VTI with particular connections.

      Attachments

        Issue Links

          depends upon

          Improvement - An improvement or enhancement to an existing feature or task. DERBY-243 connection toString should uniquely identify the connection

          • Trivial - Cosmetic problem like misspelt words or misaligned text.
          • Closed
          relates to

          Improvement - An improvement or enhancement to an existing feature or task. DERBY-293 Correlate client connection with embedded connection

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

          Activity

            People

              Unassigned Unassigned
              davidvc David Van Couvering
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated: