Hi Daniele,

I'm glad you got it to work

On Fri, Dec 21, 2018 at 7:57 PM <[email protected]> wrote:

> It worked but I don't know how robust it can be.
> Do you have any suggestion to avoid reflection to access declared fields
> in insert?
>

If you want to avoid reflection, you will have to traverse the VALUES
clause with your visit listener as well, and maintain some sort of stack
where you "remember" the visited fields of the table. This isn't trivial to
achieve and can still break. Perhaps a few integration tests would be a
more pragmatic approach. This way, you can ensure that you notice things
once they break.

A future version of jOOQ will provide a nicer object model for the internal
expression tree representation, that allows for public access to these
internals, but we're not there yet.

I hope this helps,
Lukas

-- 
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/d/optout.

Reply via email to