Thank you very much for the pointer. The VisitListener approach does appear to be a good fit for my use case and I'll pursue it. However, I'm curious, what's the motivation for not exposing the ability to get the query parts. After all jOOQ enables query building and hence one would expect to be able to get a handle to the constituent parts - similar to expecting a getXXX() method if one can invoke setXXX() on a class.
-- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/jooq-user/043f0acb-1e9b-4b9f-9ebf-0625e6cf6614%40googlegroups.com.
