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 "Suran Jayathilaka (JIRA)" <ji...@apache.org> on 2008/04/01 08:20:26 UTC

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

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

Suran Jayathilaka reassigned DERBY-1201:
----------------------------------------

    Assignee: Suran Jayathilaka

> ResultSet.updateRow() in network client should not throw an exception if no fields in the row have been modified.
> -----------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-1201
>                 URL: https://issues.apache.org/jira/browse/DERBY-1201
>             Project: Derby
>          Issue Type: Bug
>          Components: Network Client, Newcomer
>    Affects Versions: 10.1.1.0, 10.1.2.1, 10.1.3.1, 10.2.1.6
>            Reporter: David Van Couvering
>            Assignee: Suran Jayathilaka
>            Priority: Minor
>         Attachments: TestUpdateRow.java
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.