db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mamta A. Satoor (JIRA)" <derby-...@db.apache.org>
Subject [jira] Created: (DERBY-215) Correlation name not allowed for updatable columns in updatable cursors
Date Mon, 11 Apr 2005 05:09:16 GMT
Correlation name not allowed for updatable columns in updatable cursors 

         Key: DERBY-215
         URL: http://issues.apache.org/jira/browse/DERBY-215
     Project: Derby
        Type: Bug
  Components: SQL  
    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.
If you think it was sent incorrectly contact one of the administrators:
If you want more information on JIRA, or have a bug to report see:

View raw message