[jira] Commented: (DERBY-2417) Network client disallows Statement.setCursorName if an open result set is associated with the Statement object.

["Daniel John Debrunner (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/DERBY-2417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12479184 ] 

Daniel John Debrunner commented on DERBY-2417:
----------------------------------------------

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)

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

> -----------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-2417
>                 URL: https://issues.apache.org/jira/browse/DERBY-2417
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC, Network Client
>            Reporter: Daniel John Debrunner
>            Priority: Minor
>
> 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.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.