Expose PreparedStatement.setQueryTimeout as a property.

[jkerak]

Currently, after a query times out to SQL server, the query will stay running on the database, even after the thread that executed the query in the java application has closed.

Some queries may still be running hours later after they timed out. By setting the query timeout, the PreparedStatement cancels the running query after the time period has elapsed.

Is it possible to expose a parameter to set the query timeout using PreparedStatement.SetQueryTimeout(int seconds)? I believe it would need to be set as each PreparedStatement was created for execution inside Query.buildPreparedStatement().

It would be ideal if this was an optional property to set while initializing a Sql2o.

[kg29]

I am interested in taking this up. Is there a particular way you want it to be implemented?

[jkerak]

@kg29 I'm not sure exactly how it could be done, but it would be nice if it was a property you could set when creating a new Sql2o object, at the same time as connection string information. I'd be glad to help as well.

[kg29]

I have a pull request out for this. #276

[barrywilks7]

+1 would also like to see this implemented. An effectively infinite query timeout is occasionally causing our kafka consumer to be rejected from the broker. I believe this setting would allow us to control that.

[tlamatiniisrael]

Hi, I've done this, and its set as the setParameter method, since the buildPreparedStatement method, is called when you execute the Query.