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
[EMAIL PROTECTED] 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.
