db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-3249) Statement.getGeneratedKeys can return ResultSets that are not CONCUR_READ_ONLY if the Statement object has no CONCUR_READ_ONLY concurrency
Date Mon, 06 Jul 2009 15:12:14 GMT

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

Kathey Marsden updated DERBY-3249:
----------------------------------

      Issue & fix info: [Repro attached]
               Urgency: Normal
    Bug behavior facts: [Deviation from standard]

Triaged for 10.5.2. Set urgency normal, repro attached and deviation from standard.


> Statement.getGeneratedKeys can return ResultSets that are not CONCUR_READ_ONLY if the
Statement object has no CONCUR_READ_ONLY concurrency
> ------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-3249
>                 URL: https://issues.apache.org/jira/browse/DERBY-3249
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC
>            Reporter: Daniel John Debrunner
>            Priority: Minor
>
> JDBC 4 section 13.6 states:
>  The concurrency of the ResultSet object returned by getGeneratedKeys must be CONCUR_READ_ONLY.
The type of the ResultSet object must be either TYPE_FORWARD_ONLY or TYPE_SCROLL_INSENSITIVE.
> Since in some cases Derby generates the generated keys ResultSet using the Statement
object it inherits the concurrency and type of that statement.

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