Thanks a lot for your report. You're right, I can reproduce the problem. The problem went undetected because the integration tests for #5537 only checked for compilation errors in code produced by that particular code generation flag, not for this particular runtime problem.
I have created an issue for this: https://github.com/jOOQ/jOOQ/issues/7554 Will fix the issue with high priority. By the end of next week, jOOQ 3.11.1 will ship with a fix. In the meantime, the workaround is to turn on the flag again. Thanks again, Lukas Am Fr., 8. Juni 2018 um 03:11 Uhr schrieb Beldrew <[email protected]>: > A change (#5537) stops the generation of Keys.java when set to false. > However UpdatableRecordImpl calls "getPrimaryKey().getFieldsArray()" on > line 164 which ends up calling the default getPrimaryKey() in AbstractTable > which returns returns null causing a null pointer exception. > > It looks like the code generator is assuming Keys exists, and not > generating overloads for getPrimaryKey() if it doesn't. > > -- > 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. > -- 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.
