[
https://issues.apache.org/jira/browse/DERBY-1201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12591615#action_12591615
]
Dag H. Wanvik commented on DERBY-1201:
--------------------------------------
-1.
I think this issue is old and can be closed; Derby seems correct, from 10.3 at
least.
If the result set is updatable, Derby does not throw in either
network client or embedded cases. as far as I can tell. The repro as it stands,
uses a read-only result set,
in which case updateRow is always an error. If I modify the result set to be
updatable,
updateRow becomes a no-op (as required by JDBC4).
The patch makes the repro not throw for the read-only case, which is wrong, I
think.
> 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.
