"Mayuresh Nirhali (JIRA)" <[EMAIL PROTECTED]> writes:
> 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.
I think to not throw is the right behavior, cf. quote from updateRow
in API in Java 6:
Throws: SQLException - if a database access error occurs or if this
method is called when the cursor is on the insert row
Neither of these conditions apply. Aside: Generally, meaningful no-ops
are good, they grease API "algebra" like zero elements in math ;)
Dag
>
> 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.
