Timeline for Log SQL that is communicated with the database
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 1, 2013 at 9:08 | comment | added | Frank M. | Cool. Sounds interesting.. But i think you need stacktrace in every case. | |
| Jul 31, 2013 at 18:15 | comment | added | ProgrammingPanda | M, I want to be able to get access to this information runtime. Like it comes along as a metadata of the query. the issue is here stackoverflow.com/questions/17954848/… | |
| Jul 31, 2013 at 7:45 | comment | added | Frank M. | in code.google.com/p/jdbcdslog/wiki/UserGuide you can find in section Configuration parameters parameter jdbcdslog.printStackTrace. in stackTrace you can find calling class and method. | |
| Jul 30, 2013 at 19:31 | vote | accept | ProgrammingPanda | ||
| Jul 30, 2013 at 17:36 | comment | added | ProgrammingPanda | Thank you for your reply. Is there a way by which I can get the class from which the query was fired. There is a %C parameter that can be used with Log4j pattern Layout which can give us the class from which the query was fired, but it does not give me the required class when used with jdbcdslog. | |
| Jul 30, 2013 at 7:07 | history | answered | Frank M. | CC BY-SA 3.0 |