Hi Vladislav, I've given this some more thought, and I finally came to the conclusion that I could make this a feature along with my plans to generalise logging: http://sourceforge.net/apps/trac/jooq/ticket/139
My original plans were to have a generic logging interface with a default implementation (binding to SLF4J). Users can override that implementation and hook into jOOQ in order to intercept all logging events. With your suggestions, the logging events could contain QueryParts and Stores instead of plain strings, such that client code has more information about what's going on. In the end, I think you are right. There are quite a few interesting use cases not directly related to jOOQ itself, but to SQL profiling and tracing. Let's see if this can make it in 1.6.x Cheers Lukas 2011/5/17 Lukas Eder <lukas.e...@gmail.com>: > On the other hand, I might be able to just add another hook similar to > the currently being developed deserialisation magic, as discussed in > this thread: > http://groups.google.com/group/jooq-user/browse_thread/thread/d33e9a902707d111 > > Once a query has been properly attached, it can indeed communicate > execution to other listeners... I'll sleep over it >
