Great! Thanks for the immediate feedback and help!
> As a workaround, you can specify the <inputSchema/> configuration to
include only your schema.
OK. Specification of
inputSchema = 'PUBLIC'
in the database section of the generator is possible and prevents
generation of classes for tables in the information_schema.
> Are those JPA-annotated entities on the jOOQ code generator's classpath?
Good question. No, these classes were not on the class path! I just added
them, and now code is generated, and due to the above inputSchema
definition only for the public schema.
> There's always the possibility of falling back to using the standalone
code generator from within Gradle (using the latest jOOQ version):
I tried to invoke the converter from the command line as described in
http://www.jooq.org/doc/3.8/manual/getting-started/tutorials/jooq-in-7-steps/jooq-in-7-steps-step3/,
but I gave up at some point as I had to add too many jar files on the class
path (the whole dependency to hibernate in case of the JPADatabase).
But my example works now, which is great!
I will demonstrate that in the next lecture (in a course on JPA...)
Thanks again
Dominik
--
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.
