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

Different behavior in Client and Embedded modes when update on an invalid cursor

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 10.7.1.1
    • 10.7.1.1
    • JDBC
    • None
    • Embedded/Client difference

    Description

      Consider the sql snippet below:

      create table test(c1 int, c2 int);
      insert into test values(1,1);
      update test set c1=2 where current of jdk4;

      for the 'update' line, we get 'ERROR XJ202: Invalid cursor name 'JDK4'. ' in Client mode, while 'ERROR 42X30: Cursor 'JDK4' not found. Verify that autocommit is OFF.' in Embed mode.

      Attachments

        1. derby-4777.patch
          2 kB
          Yun Lee
        2. derby-4777.stat
          0.1 kB
          Yun Lee
        3. DERBY-4777_b.stat
          0.3 kB
          Myrna van Lunteren
        4. DERBY-4777_b.diff
          3 kB
          Myrna van Lunteren
        5. derby-4777-releasenote.patch
          2 kB
          Yun Lee
        6. derby-4777-releasenote.stat
          0.0 kB
          Yun Lee
        7. releaseNote.html
          5 kB
          Myrna van Lunteren
        8. releaseNote.html
          4 kB
          Richard N. Hillegas

        Issue Links

          Activity

            People

              yunlee Yun Lee
              yunlee Yun Lee
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: