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

different results with network server vs. embedded on select from a temporary table with resultset cursor hold over commit

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 10.6.1.0
    • Fix Version/s: None
    • Component/s: JDBC
    • Urgency:
      Low
    • Issue & fix info:
      Repro attached
    • Bug behavior facts:
      Embedded/Client difference

      Description

      Found this during review of conversion of declareGlobalTempTableJavaJDBC30 to junit (DERBY-2895) - when I tried to run the test with network server:

      We define a statement like so:
      Statement s1 = conn.createStatement(ResultSet.TYPE_FORWARD_ONLY, ResultSet.CONCUR_READ_ONLY,
      ResultSet.HOLD_CURSORS_OVER_COMMIT );
      and global temp table like so:
      s1.executeUpdate("declare global temporary table SESSION.t1(c11 int, c12 int) on commit delete rows not logged");

      Then, we insert 2 rows, open a result set that selects *, then do commit.
      With a new resultset, we do another select, which with network server gives 0 rows, but with embedded, 2.

        Attachments

        1. repro_d4373.java
          4 kB
          Myrna van Lunteren

          Issue Links

            Activity

              People

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

                Dates

                • Created:
                  Updated: