Derby
  1. Derby
  2. DERBY-3037

Language ResultSet.finish() is called even when the ResultSet is going to be re-used.

    Details

    • Type: Bug Bug
    • Status: Reopened
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 10.4.1.3
    • Fix Version/s: 10.3.3.1
    • Component/s: SQL
    • Labels:
      None
    • Urgency:
      Normal
    • Issue & fix info:
      Repro attached

      Description

      DERBY-827 (correctly) changed the lifetime of the language ResultSet tree to be the lifetime of the activation, but did not fix up the correct calls to ResultSet.close() and ResultSet.finish().

      A language ResultSet's lifetime should be driven by the activation, so activation.close() should call finish() on its ResultSet.

      EmbedResultSet should call close on its language ResultSet (theResults field) when the JDBC ResultSet is closed, it should not be calling finish() on its ResultSet.

      See comments in DERBY-827 for some more details and issues.

      1. DERBY_3304_Repro.java
        2 kB
        Mamta A. Satoor
      2. DERBY3037_patch_not_ready_for_commit_v2_stat.txt
        0.2 kB
        Mamta A. Satoor
      3. DERBY3037_patch_not_ready_for_commit_v2_diff.txt
        1.0 kB
        Mamta A. Satoor
      4. Derby_3037_AlterTableConstantActionChanges_v1_stat.txt
        0.2 kB
        Mamta A. Satoor
      5. Derby_3037_AlterTableConstantActionChanges_v1_diff.txt
        1 kB
        Mamta A. Satoor

        Issue Links

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              Daniel John Debrunner
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:

                Development