db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Satheesh Bandaram <sathe...@Sourcery.Org>
Subject Re: DERBY-31: More on semantics for Statement.setQueryTimeout: ResultSet.updateRow
Date Thu, 26 May 2005 18:52:18 GMT
I agree. While it is possible for updateRow() and deleteRow() to take
sometime, this may not be very common.

Satheesh

Oyvind.Bakksjo@Sun.COM wrote:

> Previously, we agreed that the query timeout should apply to
> Statement.execute() as well as each individual call to ResultSet.next().
>
> New question: Should the query timeout apply to ResultSet.updateRow()
> as well. For orthogonality, the question (although this is more of
> theoretical interest) also applies to ResultSet.deleteRow()?
>
> My initial gut feeling is that it should not; even though updating
> e.g. a large blob may take a while, I still think timing out on an
> operation like this would be more annoying than useful to the user.
>


Mime
View raw message