db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Satheesh Bandaram <sathe...@Sourcery.Org>
Subject Re: [jira] Created: (DERBY-505) Add system procedure to allow setting statement timeout
Date Tue, 16 Aug 2005 17:21:51 GMT
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
  <title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
I agree with these comments... In fact, I added similar comments to the
bug on 14th Aug. In case Jira didn't send that message out, here it is:<br>
<div class="action-body">
<blockquote>I would like to hear reasoning behind this new feature
request. I see following issues with the suggestion: <br>
  <br>
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. <br>
  <br>
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 JDBC. <br>
  <br>
</blockquote>
</div>
Satheesh<br>
<br>
Mike Matrigali wrote:<br>
<blockquote cite="mid43021CA5.8000204@sbcglobal.net" type="cite">
  <pre wrap="">I am wondering why this is necessary, since there is a way to do
this through jdbc - why add a different way to do this?  I assume
users could always create their own procedure if they needed it.
What is the circumstance that you need this from SQL rather
than JDBC.

To me this just doesn't seem like the right use of the derby
provided system procedures.

We added the system utility system procedures as a last resort
for the things which had no sql standard, like backup and import.  Any
use of system procedure is non-standard and will cause issues for
database portability, so I think it is important to not add to them
if it is not necessary.

If there really is a need to do this from sql rather than jdbc
I would prefer in the following order:
1) let users create their own procedure using existing available syntax
2) do the setting as a property rather than a system procedure


Oyvind Bakksjo (JIRA) wrote:

  </pre>
  <blockquote type="cite">
    <pre wrap="">Add system procedure to allow setting statement timeout
-------------------------------------------------------

         Key: DERBY-505
         URL: <a class="moz-txt-link-freetext" href="http://issues.apache.org/jira/browse/DERBY-505">http://issues.apache.org/jira/browse/DERBY-505</a>
     Project: Derby
        Type: New Feature
  Components: SQL  
    Versions: 10.1.1.0    
    Reporter: Oyvind Bakksjo
 Assigned to: 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.

    </pre>
  </blockquote>
  <pre wrap=""><!---->


  </pre>
</blockquote>
</body>
</html>


Mime
View raw message