[ http://issues.apache.org/jira/browse/DERBY-505?page=all ]
Oyvind Bakksjo closed DERBY-505:
--------------------------------
Resolution: Won't Fix
No interest in this functionality. Use JDBC instead.
> Add system procedure to allow setting statement timeout
> -------------------------------------------------------
>
> Key: DERBY-505
> URL: http://issues.apache.org/jira/browse/DERBY-505
> Project: Derby
> Type: New Feature
> Components: SQL
> Versions: 10.1.1.0
> Reporter: Oyvind Bakksjo
> Assignee: Oyvind Bakksjo
> Priority: Minor
>
> Propose to add a system procedure:
> SYSCS_UTIL.SYSCS_SET_STATEMENT_TIMEOUT(INT)
> This procedure will enable the query timeout functionality not only through
> JDBC, but also through SQL. I suggest the following semantics:
> The timeout value (in seconds) set with this procedure will apply to all
> subsequent statements executed on the current connection (the same connection
> on which the procedure was called), until a different value is set with the
> same procedure. A value of 0 indicates no timeout. Supplying a negative value
> will cause an exception. For each executed statement, the semantics are the
> same as for using Statement.setQueryTimeout() through JDBC.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
