Derby
  1. Derby
  2. DERBY-6261

test getCurConnJdbc20.sql is no longer useful and can be removed

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Trivial Trivial
    • Resolution: Fixed
    • Affects Version/s: 10.11.1.1
    • Fix Version/s: 10.11.1.1
    • Component/s: Test
    • Labels:
      None

      Description

      The old harness style test jdbcapi/getCurConnJdbc20.sql is the last test remaining in the jdbc20 suite.
      It runs with jdk12test=true, meaning with any jvm higher than 1.1.
      It creates a table, creates a procedure and executes it, then drops the table and procedure.
      The comment before running the function says:
      – now lets try a variety of errors
      However, the function is util.Jdbc20Test.newToJdbc20Method, but all this does is:
      Statement stmt = conn.createStatement(ResultSet.TYPE_SCROLL_INSENSITIVE,
      ResultSet.CONCUR_READ_ONLY);
      I don't see this doing anything more useful.
      Perhaps more interesting things were planned but never implemented, this type of statement is also created and tested in jdbcapi.ResultSetJdbc30Test, and we don't support anything older than 1.6 now anymore, so this test can just go.

        Activity

          People

          • Assignee:
            Myrna van Lunteren
            Reporter:
            Myrna van Lunteren
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development