New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NPE "Error while fetching indexes" while generating code for function based indexes #6620
Comments
That was quick - the release of 3.10 has not even been announced yet :) Thanks for your report. How can this be reproduced? Is there any specific index configuration that you have? |
Side-note: If there is any exception in any part of jOOQ-meta, we'll just skip that part (e.g. finding indexes), as the rest of the code generation output might still be useful. |
Yes, I was now able to isolate the error to this:
(note the index on |
Oh, interesting, a function based index. Thanks for the pointer. I can reproduce it now. Will fix ASAP! |
You're welcome. We've just today been rewriting some queries to run on Postgres 9.3+ instead of just 9.5+ and I was hoping some of the incoming INSERT ... ON CONFLICT DO goodness would help us. No luck :(. At least I could help you. As always, thanks for your product and your support! |
But |
This issue is related to #6310 (Add support for function-based indexes in code generator) |
In fact, this isn't PostgreSQL specific |
Yeah, exactly. 9.3 gets some emulation instead (the rest of the queries we're rewriting, what a pain), and there I was hoping for a change :). |
Would you mind creating a new issue, though? It's not related to this NPE |
Thanks again for reporting this. We'll release 3.10.1 soon with a fix (#6624) |
The fix for this issue has now been released in 3.10.1 |
Related problem (Oracle only): #7824 |
Expected behavior and actual behavior:
While generating jOOQ code with the new 3.10, an error shows up the Maven output. The build succeeds, though, and code is generated (?!).
Steps to reproduce the problem:
Run the
jooq-codegen-maven
.Versions:
The text was updated successfully, but these errors were encountered: