db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lance J. Andersen" <Lance.Ander...@Sun.COM>
Subject Re: DERBY-31: More on semantics for Statement.setQueryTimeout: ResultSet.updateRow
Date Tue, 07 Jun 2005 21:36:32 GMT
you are correct,  timeouts are not documented to effect xxxRow() 
specifically in the jdbc 3 or 4 spec

David Van Couvering wrote:

> I'm guessing the JDBC spec doesn't have anything to say about this?
> Do we know what other drivers do for updateRow() and deleteRow()?
> Barring any existing explicit or implicit standard behavior, my 
> feeling is that any method that results in a remote round-trip should 
> support a timeout.  I have dealt with too many applications where the 
> application hangs if for some reason the remote service is not 
> responding.
> Thanks,
> David
> 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.

View raw message