[
https://issues.apache.org/jira/browse/DERBY-1201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mayuresh Nirhali updated DERBY-1201:
------------------------------------
Attachment: TestUpdateRow.java
This issue is reproducible on 10.2.2, but not on 10.3 trunk. repro is attached.
The behavior on trunk is consistent, but both the implementations throw
exception now. In the description it is hinted that both modes should be silent
for such case.
If community agress that throwing exception in this case is the right behavior,
we can close this bug as invalid/Not reproducible.
Hoping that someone else could comment on this.
> 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
> 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.
