db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dag H. Wanvik (JIRA)" <derby-...@db.apache.org>
Subject [jira] Created: (DERBY-1312) refreshRow behavior not the same in Derby client and embedded drivers
Date Tue, 09 May 2006 23:44:06 GMT
refreshRow behavior not the same in Derby client and embedded drivers

         Key: DERBY-1312
         URL: http://issues.apache.org/jira/browse/DERBY-1312
     Project: Derby
        Type: Improvement

  Components: JDBC, Network Client  
    Reporter: Dag H. Wanvik
    Priority: Minor
     Fix For:

In the embedded client, ResultSet#refreshRow throws a not implemented
exception.  In the client driver, it is implemented as a no-op (*) for
the updatable result set types we support, although it has some cruft
for sensitive result sets - from a previous life?

(*) Checks are performed to see if the method is callable given the
state of the result set, but no actual refresh is attempted. This is
correct for scroll insensitive result sets, btw.

The client implementation is wrong in another respect: (Quote from
JDBC 3.0 API javadoc):

"If refreshRow is called after calling an updater method, but before
calling the method updateRow, then the updates made to the row are

As far as I can see, since this is implemented as a no-op, this
implicit update canceling does not happen.

I think we should reconcile the driver behaviors, probably by having
the client throw a not implemented exception as well.  It is not
really needed for scroll insensitive result sets.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message