> There are tradeoffs everywhere though, so with Jooq you still aren't 1-to-1 with raw SQL You're probably hinting at writing derived tables / CTEs? jOOQ will

> There are tradeoffs everywhere though, so with Jooq you still aren't 1-to-1 with raw SQL You're probably hinting at writing derived tables / CTEs? jOOQ will never keep you from writing views and table valued functions, though. It encourages you do so! Those objects play very well with code generation, and you can keep jOOQ for the dynamic parts, views/functions for the static parts.