You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ibatis.apache.org by "Claus Ibsen (JIRA)" <ib...@incubator.apache.org> on 2007/02/16 11:30:05 UTC

[jira] Commented: (IBATIS-99) Add logging of long running SQL statements

    [ https://issues.apache.org/jira/browse/IBATIS-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12473667 ] 

Claus Ibsen commented on IBATIS-99:
-----------------------------------

I have been on numerous projects where we had really long running SQL that got out of hand.
Since Oracle on long the SQL when the query ends the operation staff could not always give examples.
And Oracle did not log the bind parameters so it was hard to find the culprits among the many millions of SQL executed every day.

We ended build in some SQL logging where we could set a min time value for the long running SQL's to be logged (with bind parameters outputted also).

> Add logging of long running SQL statements
> ------------------------------------------
>
>                 Key: IBATIS-99
>                 URL: https://issues.apache.org/jira/browse/IBATIS-99
>             Project: iBatis for Java
>          Issue Type: New Feature
>          Components: SQL Maps
>            Reporter: Larry Meadors
>            Priority: Trivial
>
> It would be useful to have a way to log long running statements. 
> Ideally, the implementation would allow us to define a global value for the definition of "long running", and maybe a per statement definition, too.

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