db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-4045) Subquery causes error: 'updateString' not allowed because the ResultSet is not an updatable ResultSet
Date Tue, 03 Feb 2009 15:10:03 GMT

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

Knut Anders Hatlen commented on DERBY-4045:
-------------------------------------------

Kim, I think the doc will have to be changed anyway, since a fix of the SQL will probably
not allow all kinds of subqueries in WHERE clauses. So for now it would be fine to update
the doc with a bullet saying what you suggested above. If we change the SQL later, the sentence
could be changed to specify which kinds of subqueries we don't allow. We could perhaps change
the documentation in a separate issue and leave this one open to track the request for the
SQL change.

> Subquery causes error: 'updateString' not allowed because the ResultSet is not an updatable
ResultSet
> -----------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-4045
>                 URL: https://issues.apache.org/jira/browse/DERBY-4045
>             Project: Derby
>          Issue Type: Bug
>          Components: Documentation, SQL
>            Reporter: John T. Dow
>
> Embedded Derby (don't know about client) demoted an updatable result set apparently due
to a nested query.
> select * from orders where (orders.recordno = (select max(orders.recordno) from orders))
> Fix if possible. 
> If it can't be fixed, the documentation should be changed.

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