db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Satheesh Bandaram (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-505) Add system procedure to allow setting statement timeout
Date Sun, 14 Aug 2005 00:22:54 GMT
    [ http://issues.apache.org/jira/browse/DERBY-505?page=comments#action_12318727 ] 

Satheesh Bandaram commented on DERBY-505:

I would like to hear reasoning behind this new feature request. I see following issues with
the suggestion:

1) System procedures and functions are used for admin and diagnostic purposes typically. Since
there is no standard for these, every database vendor has their own way to perform admin and
diagnostics. However, this proposal seems to define application behavior based on system procedure.

2) I would like to know why JDBC's setQueryTimeout mechanism is not sufficient... Not sure
what the bug comment means by "query timeout functionality not only through JDBC, but also
through SQL". Derby supports SQL only using JDBC currently. If the comment is refering to
IJ, that is also a JDBC application and could be programmed to support query timeout using

> 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:
>     Reporter: Oyvind Bakksjo
>     Assignee: Oyvind Bakksjo
>     Priority: Minor

> Propose to add a system procedure:
> 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:
For more information on JIRA, see:

View raw message