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.
