Hi Darren, This is indeed a bit unfortunate, thanks for reporting. I think the default implementation should be fixed, preventing excessive logging in the event of LOB (or VARCHAR) content. This should be easy to fix through a couple of adaptations to the renderers. I have registered #2939 for this: https://github.com/jOOQ/jOOQ/issues/2939
This fix will probably also be merged to jOOQ 3.2.3 Cheers Lukas 2014/1/8 Darren S <[email protected]> > First off, let me say I love the logging in jOOQ, very useful. But I've > hit a bit of problem. The issue I have is that when the variables are > bound, for one specific query I have, the SQL is too long. It ends up > printing megabytes of content (it has a MySQL MEDIUMTEXT field in it). > This in turn ends up crashing the Eclipse console view. > > So what I've done is extended the LoggerListener.renderEnd() and put in > logic to not print the bind variable text if its longer than a certain > number of characters. I then disable execution logging and add my own > ExecuteListeners. Now this is working basically fine. What I was wonder > is if there is a better way to do this? I was thinking maybe two different > approaches. > > 1) During the rendering of the SQL, somehow limit the bound variables text > to a certain width > 2) Log the bind SQL text to a different logger and then use logback to > limit the message width "%.100m" > > Thoughts? > > Darren > > -- > You received this message because you are subscribed to the Google Groups > "jOOQ User Group" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "jOOQ User Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
