You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Daniel John Debrunner (JIRA)" <ji...@apache.org> on 2007/12/04 20:07:43 UTC

[jira] Created: (DERBY-3249) Statement.getGeneratedKeys can return ResultSets that are not CONCUR_READ_ONLY if the Statement object has no CONCUR_READ_ONLY concurrency

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.


[jira] Commented: (DERBY-3249) Statement.getGeneratedKeys can return ResultSets that are not CONCUR_READ_ONLY if the Statement object has no CONCUR_READ_ONLY concurrency

Posted by "Daniel John Debrunner (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/DERBY-3249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12548362 ] 

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

Test jdbc.AutoGenJDBC30Test has some commented out code that shows this bug, search for DERBY-3249.

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


[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

Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
     [ 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.