Dear community, I've finally implemented what was overdue after I had met Mike Ernst some years ago at a conference speaker's dinner. The new jOOQ-checker module. It leverages JSR-308 and the Checker Framework to help users validate that their Oracle-only DAOs truly work with Oracle, that their H2/PostgreSQL services really work on both those databases, etc.
How this works? I've written up a blog post here: https://blog.jooq.org/2016/05/09/jsr-308-and-the-checker-framework-add-even-more-typesafety-to-jooq-3-9 Essentially, you simply annotate your packages / classes / methods with @Allow and/or @Require annotations, and from then on, those packages / classes / methods compile only with the allowed and/or required SQLDialects. This already works before jOOQ 3.9 will be released in Q3 2016. You can download and compile the module directly from GitHub and use it with any jOOQ version: https://github.com/jOOQ/jOOQ/tree/master/jOOQ-checker What I'd love to know *before *releasing jOOQ 3.9 is your early feedback. 1. Is the checker algorithm useful? Or is it too complicated? Or is it missing things? 2. Are there any bugs in the checker? 3. Are there any bugs in the API (e.g. wrong or missing @Support annotations) 4. Do you see any other checkers than the PlainSQLChecker and SQLDialectChecker that could be useful? 5. Any other feedback? Looking forward to your feedback, 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.
