[ http://issues.apache.org/jira/browse/IBATIS-22?page=comments#action_12418441 ]
Doug Duong commented on IBATIS-22: ---------------------------------- 1. Could the new support be applied in this case? - if a statement is called in a special context, it must not last longer than n seconds - if the same statement above is called in another context, there's no timeout constraint for it then 2. I've just had a quick glance at the latest code on SVN, it seems that the timeout can be specified for each statement in the sqlmap xml. It means that if a statement has a dynamic timeout, we have to duplicate the statement definition and specify different timeout values for each statement. Is that right? 3. This leads to a new open point for iBatis sqlmap xml: can statement definitions be extended, to avoid duplications like this case? It seems that statement definitions should be extended only to specify another properties (timeout, resultMap, parameterClass, ...), not to change their sql content. Thank you very much. > Specify Query Timeout > --------------------- > > Key: IBATIS-22 > URL: http://issues.apache.org/jira/browse/IBATIS-22 > Project: iBatis for Java > Type: New Feature > Components: SQL Maps > Reporter: Rahul Kapoor > Assignee: Jeff Butler > Fix For: 2.2.0 > > There seems to be no current way to specify timeouts for select statements. I > did see a message in the sf forum that using driver properties is a possible > workaround. But it would be really nice to have a per statement timeout. -- 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
