db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-2417) Network client disallows Statement.setCursorName if an open result set is associated with the Statement object.
Date Mon, 06 Jul 2009 20:11:14 GMT

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

Rick Hillegas updated DERBY-2417:
---------------------------------

               Urgency: Normal
    Bug behavior facts: [Embedded/Client difference]
               Summary: Network client disallows Statement.setCursorName if an open result
set is associated with the Statement object.  (was: Network client disallows Statement.setCursorName
if an open result set is associated with the Statement object.
)

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

> 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.


Mime
View raw message