Hi Lukas, > Let's summarise. In essence both you - and at the time Vladislav > Rastrusny - are asking for a simple listener API that is invoked by > jOOQ every time jOOQ performs some JDBC operation. To make things more > concise, this API is implemented by default by the existing > JooqLogger.
If the JooqLogger is a particular type of listeners, then the cost of logging is there all the time (wrapped result sets, event creation and notification, parameter analysis, etc.). I would favor a no-cost API when there are no listeners which is the most common case I think. > Probably, this is best implemented using the new runtime configuration > that I'm adding for jOOQ 2.0.5. To every Factory, you can add a list > of classes that jOOQ should initialise and make calls to. Factory is not multi threaded, so a program does not have a single factory. One of the strengths of the tool we have is that we can just launch it and activate logging: it registers statically and listens to everything. This is especially important because one thread may be performing a call which can explain delays for another thread. I don't deny that logging a particular factory is not useful, I am just highlighting the fact that being able to listen to everything is generally more desirable. -Christopher
