db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suran Jayathilaka (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-1201) ResultSet.updateRow() in network client should not throw an exception if no fields in the row have been modified.
Date Sun, 20 Apr 2008 09:36:27 GMT

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

Suran Jayathilaka updated DERBY-1201:
-------------------------------------

    Attachment: derby-1201.diff

Makes the above suggested changes to check if the row has actually been updated. 

Please review.

> 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: derby-1201.diff, 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.


Mime
View raw message