db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lukas Eder (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-4138) Adding an "ORDER BY" clause breaks updatable result sets
Date Fri, 24 May 2013 17:06:21 GMT

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

Lukas Eder commented on DERBY-4138:
-----------------------------------

See also DERBY-6228, where adding an ORDER BY clause to a SELECT [LOB column] query terminates
the connection
                
> Adding an "ORDER BY" clause breaks updatable result sets
> --------------------------------------------------------
>
>                 Key: DERBY-4138
>                 URL: https://issues.apache.org/jira/browse/DERBY-4138
>             Project: Derby
>          Issue Type: Improvement
>          Components: JDBC
>    Affects Versions: 10.4.2.0
>         Environment: Solaris
>            Reporter: Alan Burlison
>            Priority: Minor
>
> The following doesn't work:
> ps = c.prepareStatement("select a, b, c from tab where a = ? order by b desc",
>   ResultSet.TYPE_SCROLL_INSENSITIVE, ResultSet.CONCUR_UPDATABLE);
> :
> :
> rs.updateInt(3, 123);
> and throws the following exception:
> 'updateInt' not allowed because the ResultSet is not an updatable ResultSet. [XJ083]
> Removing the 'order by b desc' clause makes the problem go away.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message