Well, I guess we could suppress the stack trace for unknown functions by specifying Settings.parseUnknownFunctions = IGNORE. We already parse known functions (e.g. UPPER()) and ignore them later on, due to function based indexes not being supported. So, this particular parser error doesn't add much value. Even if we parsed the function, the index would be ignored.
I'll improve this for jOOQ 3.15: https://github.com/jOOQ/jOOQ/issues/11977 Thanks again for your report. Lukas On Wed, Jun 9, 2021 at 9:15 AM Rob Sargent <[email protected]> wrote: > roger that. Thank you. > > On 6/9/21 1:13 AM, Lukas Eder wrote: > > The code generator doesn't support function based indexes yet: > > https://github.com/jOOQ/jOOQ/issues/6310 > > <https://github.com/jOOQ/jOOQ/issues/6310> > > > > But we're still trying to parse expressions in case they're not > > actually functions, but just alternative spellings of columns: > > https://github.com/jOOQ/jOOQ/issues/11047 > > <https://github.com/jOOQ/jOOQ/issues/11047> > > > > The logging of the exception and stack trace were done to help people > > report any further issues / oversights / edge cases in this area, > > which might not be related to function based indexes. > > > > 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]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jooq-user/70d5319f-b556-ed40-a48a-5e0d3a7411e4%40gmail.com > . > -- 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/CAB4ELO5CQAPJXROtSyZLuzFHxdJjUXu-D4O40tMh3xwnsQbN9Q%40mail.gmail.com.
