[ http://issues.apache.org/jira/browse/IBATIS-151?page=comments#action_12313417 ]
Brandon Goodin commented on IBATIS-151: --------------------------------------- I would prefer to only time the sql execution. Timing logs should only deal with areas that the developer actualy codes. The developer can test their own code in front of ibatis for speed and ibatis can help time their code execution time behind ibatis (i.e. sql execution time). The developer can also start a timer before calling ibatis and check those times in conjunction with the sql execution times to determine if there is a problem somewhere between their code and their sql execution (i.e. within ibatis). But, i do not think we should put logging in ibatis that tests it's own performance. As previously stated... that would denegrate performance and may produce unnecessary alarm. > Detailed logs for statement execution > ------------------------------------- > > Key: IBATIS-151 > URL: http://issues.apache.org/jira/browse/IBATIS-151 > Project: iBatis for Java > Type: New Feature > Components: SQL Maps > Versions: 2.0.9b > Reporter: Vernon Wong > Priority: Minor > > There are currently no logs during the SQLMap execution that captures the > execution time of the statement and the object generation time by SQLMap. > These performance logs can help to provide useful information on the > statements usage and performance, without the influence of object creation > time. -- 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
