Hi, I am Deepa Remesh and I work for IBM. I am just starting to work on Derby and was trying to apply the patch for DERBY-31. I noticed that the file QueryTimer.java is not in the patch file but is attached separately. I had to manually add it to the Eclipse project before compiling. It would be good if this file is added to the patch.
Thanks, Deepa On 6/15/05, Oyvind Bakksjo (JIRA) <[email protected]> wrote: > [ http://issues.apache.org/jira/browse/DERBY-31?page=all ] > > Oyvind Bakksjo updated DERBY-31: > -------------------------------- > > Attachment: DERBY-31.svn.status > DERBY-31.svn.diff > derbyall_report.txt > > Attached patch addresses the following issues: > * Throw exception on negative input to setQueryTimeout() > * Test case for the above > * Use milliseconds instead of seconds in the PreparedStatement interface and > GenericPreparedStatement class > * Exclude SetQueryTimeoutTest from DerbyNet and DerbyNetClient, since these > environments don't yet support the new functionality (will create a fix for > the DerbyClient driver later > > Derbyall has been run with two failures, report attached. > StmtCloseFunTest - hard to tell if it's related to my changes, very little > output from the test about what exactly failed. > miscerrors - doesn't seem related > > > > Statement.setQueryTimeout() support. > > ------------------------------------ > > > > Key: DERBY-31 > > URL: http://issues.apache.org/jira/browse/DERBY-31 > > Project: Derby > > Type: New Feature > > Components: JDBC > > Environment: ALL > > Reporter: Ali Demir > > Assignee: Oyvind Bakksjo > > Attachments: DERBY-31.svn.diff, DERBY-31.svn.status, Derby-31.patch, > > QueryTimer.java, derbyall_report.txt > > > > Calling Statement.setQueryTimeout() throws exception saying that function > > is not supported. This is an important JDBC feature and is limiting our > > options to use Derby with our JDBC code. Implementing this JDBC function > > would make Derby much easier to adopt. > > -- > 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 > >
