Thank you very much for your email and for your patience.
In recent months, getting better access to the jOOQ expression tree model
has been an increasingly popular feature request on all of our support
channels. Let me first state that we've recognised this need and will make
re-designing our expression tree model for internal and external use a top
priority for jOOQ 3.13. There are numerous reasons why a new, immutable
query object model will add a lot of value to everyone, specifically those
with parser use cases.
Regarding your specific use-case, I think that your workaround, trying to
find existing tables in query strings might indeed be a viable 80/20
solution (or even 95/5 if your table names are sufficiently specific). You
can, however, use jOOQ 3.12 for this already. As long as you're not
transforming your SQL, a VisitListener will probably do. A very similar
question has been asked here: https://stackoverflow.com/q/53990723/521799,
it aims for collecting field references from create table statements. See
my answer here: https://stackoverflow.com/a/54006668/521799
If you're using the jOOQ API to create your SQL statements, then you don't
even need the parser.
You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page.
To unsubscribe from this group and stop receiving emails from it send an email to [hidden email].