I don't think that the code generation itself is the bottleneck. Between subsequent generations, only deltas are re-generated (class additions / removals / changes) to allow for incremental compilation of generated code.
Probably, the queries against the dictionary views / information_schema might not be optimal. Did you measure things at your side? Is there anything particular that you found to be slow? Are you generating code against a local database on your computer, or a remote one - possibly cloud hosted one? One way to speed up code generation would be to use jOOQ's XMLDatabase, or implement your own org.jooq.util.Database from jOOQ meta, that is optimised for your specific schema. Let me know if that sounds like an option to you, and I'll explain more 2015-06-01 22:38 GMT+02:00 Robert DiFalco <[email protected]>: > While I have you, is there any simple way to speed up the code generation > phase in the maven plugin? mvn test can take a while doing the generation > each time. I only have one schema, does adding: > > <outputSchemaToDefault>true</outputSchemaToDefault> > > Save me any time? Anything else I can look at? I'm not generating beans or > anything like that. > No, that shouldn't have any impact on the code generation speed. It is just used to omit the schema in generated output, which is useful in single-schema / multi-tenant environements. -- 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.
