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: > 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 > 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. >
