Hi Lukas, I strongly think there should not be a duplication of Factory (JooqDsl) methods to the Executor type. I really think that separation of concern should prevail: - One entry point to build a query, using a query building DSL. - One entry point to rendering a query, using a query rendering DSL.
This would mean having 2 different factories (JooqDsl, JooqRenderingDsl) but this seems overkill so I think that having a "with" keyword on the JooqDsl that returns a JooqRenderingDsl instance is not that bad: import jooq.org.JooqDsl.* with(Connection, Dialect).bind(Query).fetch(); or .execute() This would greatly simplify the API, by reducing the number of exposed methods, reducing the number of ways to do the same thing, and making a clear distinction between which part of the API does what. Note that I don't think ".bind(Query)" breaks the DSL aspect of JOOQ. It is very similar to existing APIs such as ".select(Field...)". Or am I missing something? Cheers, -Christopher -- 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/groups/opt_out.
