You are viewing a plain text version of this content. The canonical link for it is here.

Posted to derby-dev@db.apache.org by "David Van Couvering (JIRA)" <de...@db.apache.org> on 2006/04/11 03:07:13 UTC

[jira] Updated: (DERBY-1201) ResultSet.updateRow() in network client should not throw an exception if no fields in the row have been modified.

     [ http://issues.apache.org/jira/browse/DERBY-1201?page=all ]

David Van Couvering updated DERBY-1201:
---------------------------------------

    Component: Newcomer

> ResultSet.updateRow() in network client should not throw an exception if no fields in the row have been modified.
> -----------------------------------------------------------------------------------------------------------------
>
>          Key: DERBY-1201
>          URL: http://issues.apache.org/jira/browse/DERBY-1201
>      Project: Derby
>         Type: Bug

>   Components: Network Client, Newcomer
>     Versions: 10.1.1.0, 10.1.1.1, 10.1.1.2, 10.1.2.0, 10.1.2.1, 10.1.2.2, 10.1.2.3, 10.2.0.0, 10.1.3.0
>     Reporter: David Van Couvering
>     Priority: Minor

>
> ResultSet.updateRow() in the network client throws an exception if no fields in the current row have been modified.  In the embedded client, the method silently does nothing in the same circumstances.  Although the spec is yet to go final, our understanding is that JDBC 4 spec indicates that the behavior of the embedded client is correct, so we should correct this in the network client.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira