You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Carl Hall (JIRA)" <ji...@apache.org> on 2015/04/14 23:29:59 UTC
[jira] [Commented] (DBUTILS-70) add setQueryTimeout support to
QueryRunner
[ https://issues.apache.org/jira/browse/DBUTILS-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14494925#comment-14494925 ]
Carl Hall commented on DBUTILS-70:
----------------------------------
Thanks for the code example, [~mabroukb]. I'll use that as the basis for adding updating the current source.
> add setQueryTimeout support to QueryRunner
> ------------------------------------------
>
> Key: DBUTILS-70
> URL: https://issues.apache.org/jira/browse/DBUTILS-70
> Project: Commons DbUtils
> Issue Type: Improvement
> Reporter: Michael Akerman
> Priority: Minor
> Fix For: 1.7
>
> Attachments: commons-dbutils-1.1.1.zip
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> java.sql.Statement and java.sql.PrepareStatement support a method called setQueryTimeout.
> It would be nice to add a public setQueryTimeout method to QueryRunner that would pass this parameter through to the underlying Statements or PreparedStatements.
> For most of my applications if a query runs longer than a few seconds, there's something wrong, and I'd like a SQLException in that scenario so I can know there's an issue.
> I'd be happy to submit some code as a proposal.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)