db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dag.Wan...@Sun.COM (Dag H. Wanvik)
Subject Re: [jira] Updated: (DERBY-1201) ResultSet.updateRow() in network client should not throw an exception if no fields in the row have been modified.
Date Fri, 08 Jun 2007 17:49:39 GMT
"Mayuresh Nirhali (JIRA)" <jira@apache.org> 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.



Mime
View raw message