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

Network client disallows Statement.setCursorName if an open result set is associated with the Statement object.

    Details

    • Type: Bug
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: 10.2.2.0
    • Fix Version/s: None
    • Component/s: JDBC, Network Client
    • Urgency:
      Normal
    • Bug behavior facts:
      Embedded/Client difference

      Description

      The Javadoc says that this cursor name applies to future execute methods so the current state of the statement object should be irrelevant.

      Embedded allows the setCursorName and applies it to future executes.

        Issue Links

          Activity

          Hide
          djd Daniel John Debrunner added a comment -

          1) testSetCursorNextExecute(org.apache.derbyTesting.functionTests.tests.lang.CursorTest)java.sql.SQLException: Operation 'setCursorName()' cannot be performed o
          n object 'Statement' because there is an open ResultSet dependent on that object
          .
          at org.apache.derby.client.am.SQLExceptionFactory.getSQLException(SQLExceptionFactory.java:46)
          at org.apache.derby.client.am.SqlException.getSQLException(SqlException.java:346)
          at org.apache.derby.client.am.Statement.setCursorName(Statement.java:801)
          at org.apache.derbyTesting.functionTests.tests.lang.CursorTest.testSetCursorNextExecute(CursorTest.java:171)

          Show
          djd Daniel John Debrunner added a comment - 1) testSetCursorNextExecute(org.apache.derbyTesting.functionTests.tests.lang.CursorTest)java.sql.SQLException: Operation 'setCursorName()' cannot be performed o n object 'Statement' because there is an open ResultSet dependent on that object . at org.apache.derby.client.am.SQLExceptionFactory.getSQLException(SQLExceptionFactory.java:46) at org.apache.derby.client.am.SqlException.getSQLException(SqlException.java:346) at org.apache.derby.client.am.Statement.setCursorName(Statement.java:801) at org.apache.derbyTesting.functionTests.tests.lang.CursorTest.testSetCursorNextExecute(CursorTest.java:171)
          Hide
          djd Daniel John Debrunner added a comment -

          CursorTest has a fixture called 'derby2417testSetCursorNextExecute' tests this issue and only runs in embedded. Once this is fixed the fixture can be run in both.

          Show
          djd Daniel John Debrunner added a comment - CursorTest has a fixture called 'derby2417testSetCursorNextExecute' tests this issue and only runs in embedded. Once this is fixed the fixture can be run in both.
          Hide
          rhillegas Rick Hillegas added a comment -

          Triaged for 10.5.2: assigned normal urgency and flagged as embedded/client difference.

          Show
          rhillegas Rick Hillegas added a comment - Triaged for 10.5.2: assigned normal urgency and flagged as embedded/client difference.

            People

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

              Dates

              • Created:
                Updated:

                Development