You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ibatis.apache.org by "cristian manea (JIRA)" <ib...@incubator.apache.org> on 2007/07/31 16:49:53 UTC

[jira] Created: (IBATISNET-235) There should be a way to specify a Timeout for a specific query, instead of using always the default.

There should be a way to specify a Timeout for a specific query, instead of using always the default.
-----------------------------------------------------------------------------------------------------

                 Key: IBATISNET-235
                 URL: https://issues.apache.org/jira/browse/IBATISNET-235
             Project: iBatis for .NET
          Issue Type: Improvement
          Components: DataMapper
    Affects Versions: DataMapper 1.6.1, DataMapper 1.6.2, DataMapper 2.0
         Environment: Microsoft Windows, DNF 2.0
            Reporter: cristian manea
            Priority: Critical


There is no way to specify a specific Timeout for a mapper query. 

This can make it blocking for an app, especially if we have some complex query used for reporting, or for search, an if the db is large enough.

It is very important to be able to say: this query should timeout in 5 secs (because it reads a record based on the index), but THIS query should timeout in 10 minutes, because it is very complex and goes in 5 tables (used for reporting, lets say). 

It is unthinkable to set the same timeout for both queries. The first one could mean that it could block my app if instead of 5 secs it would be 10 mins, and the second one would mean that I cannot do any complex query on a large DB using iBATIS.

Please think of re-implementing one or both this solutions:
1) be able to specify in the sqlmap.xml statement the timeout for the query (static timeout).
2) or be abble to specify the timeout when calling the QueryForXXXX(...) by overloading the method in order to be able to specify the timeout (dynamic timeout)

Regards.

Cristian Manea - www.atypiq.ro


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.