2017-10-31 1:54 GMT+01:00 <[email protected]>: > Thanks for taking the time to write this up. > > I did do the globalTableReferences thing. It at least eliminates the > annoyance I was feeling whenever I wrote some JOOQ code - I *knew* I was > using thing inconsistently but I didn't want to setup a static analysis > tool. I didn't really care which one was used (though it was confusing and > annoying at first when figuring out that it didn't matter). > > When I tried to do the globalObjectReferences instead, I ran into a > problem with Sequences - the global object ref is the *only* specific code > reference JOOQ generates. >
Yes, that's the sledge hammer. There's also <globalTableReferences/>... > One thing I did do in my own project structure was to factor out the JOOQ > generated code to its own Gradle sub-project that my server depends on. > This helps me quickly filter out all the JOOQ internal references when I'm > scanning the results in my IDE. > That's certainly a good idea. Also, special package namespaces can help to do that, visually. Depending on how the IDE works, of course. Thanks, Lukas -- 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.
