db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Matrigali (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-215) Correlation name not allowed for updatable columns in updatable cursors
Date Fri, 10 Jul 2009 21:47:15 GMT

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

Mike Matrigali updated DERBY-215:

               Urgency: Normal
    Bug behavior facts: [Deviation from standard]

Triaged July 10, 2009: assigned normal urgency. 

> Correlation name not allowed for updatable columns in updatable cursors
> -----------------------------------------------------------------------
>                 Key: DERBY-215
>                 URL: https://issues.apache.org/jira/browse/DERBY-215
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions:
>            Reporter: Mamta A. Satoor
> Derby supports positioned updates via direct SQL and via updatable resultset JDBC apis.

> Derby's implementation of updatable resultset JDBC api does not allow use of correlation
names for updatable columns. For eg, on a FORWARD_ONLY, CONCUR_UPDATABLE Statement object,
you can't issue statement.executeQuery("select c11 as col1, c12, c13 from t1 for update of
c11, c12"). The use of correlation name col1 for updatable column c11 will result in an exception.

> The check for this correlation name for updatable resultset jdbc api was earlier in the
run time code (ResultSet.updateXXX methods) but that check had performance implications. To
address that, the check has been moved to compile time in the CursorNode.java (this went in
as revision 159758). But CursorNode.java handles postioned updates coming though both SQL
and through updatable resultset jdbc apis and hence as a side effect of moving the check to
compile time, the positioned update through direct SQL can also NOT use correlation name for
updatable columns. This might impact existing applications.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message