|
View:
New views
3 Messages
—
Rating Filter:
Alert me
|
|
|
[jira] Created: (JDBI-13) Logging SQL before executeLogging SQL before execute
-------------------------- Key: JDBI-13 URL: http://jira.codehaus.org/browse/JDBI-13 Project: jDBI Issue Type: Improvement Components: Core Environment: Mac OS X Leopard 10.5 Java 1.5.0_13-b05-237) Reporter: Kaoru Shirai Assignee: Brian McCallister Currently, SQL logging is performed after statement is executed. So, SQL is logged only statement is executed successfully. But if execution failed (like SQL syntax error), I cannot look caused SQL up from log. How about separating a log entry into "SQL" and "took time"? SQL is logged before executing, then time is logged after executing. Thanks. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
[jira] Commented: (JDBI-13) Logging SQL before execute[ http://jira.codehaus.org/browse/JDBI-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=138995#action_138995 ] Kaoru Shirai commented on JDBI-13: ---------------------------------- Sorry... I forgot to set Affects Version... It's jDBI-2.2.2. > Logging SQL before execute > -------------------------- > > Key: JDBI-13 > URL: http://jira.codehaus.org/browse/JDBI-13 > Project: jDBI > Issue Type: Improvement > Components: Core > Environment: Mac OS X Leopard 10.5 Java 1.5.0_13-b05-237) > Reporter: Kaoru Shirai > Assignee: Brian McCallister > > Currently, SQL logging is performed after statement is executed. > So, SQL is logged only statement is executed successfully. > But if execution failed (like SQL syntax error), I cannot look caused SQL up from log. > How about separating a log entry into "SQL" and "took time"? > SQL is logged before executing, then time is logged after executing. > Thanks. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
[jira] Commented: (JDBI-13) Logging SQL before execute[ http://jira.codehaus.org/browse/JDBI-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=139094#action_139094 ] Brian McCallister commented on JDBI-13: --------------------------------------- Very good point! > Logging SQL before execute > -------------------------- > > Key: JDBI-13 > URL: http://jira.codehaus.org/browse/JDBI-13 > Project: jDBI > Issue Type: Improvement > Components: Core > Environment: Mac OS X Leopard 10.5 Java 1.5.0_13-b05-237) > Reporter: Kaoru Shirai > Assignee: Brian McCallister > > Currently, SQL logging is performed after statement is executed. > So, SQL is logged only statement is executed successfully. > But if execution failed (like SQL syntax error), I cannot look caused SQL up from log. > How about separating a log entry into "SQL" and "took time"? > SQL is logged before executing, then time is logged after executing. > Thanks. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
| Free embeddable forum powered by Nabble | Forum Help |