Though this isn't a perfect solution you could white list/ black list the set of tables that are generated.
https://www.jooq.org/doc/3.9/manual/code-generation/codegen-advanced/codegen-config-includes-excludes/ We have a ton of tables generated in legacy and would rather not generate code for in our DB, so instead we explicitly list every table we want to auto-gen. -- Samir Faci On Thu, Aug 3, 2017 at 9:19 AM, <[email protected]> wrote: > Hi, > > I'm looking for an advice on skipping views during code gen. I believe ATM > JOOQ cannot distinguish between regular tables and views. > This is creating problems in my case, where I have two schemas, let's say > A and B. B has views for all tables in A as well as its own tables unique > to B. (Don't ask me why -- legacy setup). > So when I generate code from the two schemas, for each table T in A I get > table/record/pojo objects in duplicate. While they technically don't clash > due to different package names, referring to the right object in the code > becomes error-prone. > > Why can't JOOQ distinguish between tables and views? This is supported by > JDBC's DatabaseMetaData, isn't it? > > Any alternative piece of advice? > > Thanks! > --Ernest > > -- > 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. > -- Thank you Samir Faci https://keybase.io/csgeek -- 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.
