db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alan Burlison (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-4138) Adding an "ORDER BY" clause breaks updatable result sets
Date Wed, 01 Apr 2009 13:39:13 GMT

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

Alan Burlison updated DERBY-4138:
---------------------------------

    Priority: Trivial  (was: Major)
     Urgency: Low  (was: Urgent)

Huh, so it does.  Whilst I can understand why a subselect might be problematic, not being
able to use a simple 'order by' seems arbitrarily restrictive.

> 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: Bug
>          Components: JDBC
>    Affects Versions: 10.4.2.0
>         Environment: Solaris
>            Reporter: Alan Burlison
>            Priority: Trivial
>
> 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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message