Before I got the answer that I didn't need a connection to instantiate the JOOQ Factory, I had resorted to a modified version of this with a seperate JooqExecutorFactory handling the connection getting and closing, and providng a JooqExecutor used execute the DSL. This seemed more awkward to me and created more boilerplate of own boilerplate, and I went back to the single class approach once I knew I didn't have to have the connection up front. However thinking about it now, there may be value in this second option for cases where you want to execute several commands through jooq, which using the single-class version I pasted above, would get and close a connection for each operation.
- jooq dsl without a connection? ericjs
- Re: jooq dsl without a connection? Lukas Eder
- Re: jooq dsl without a connection? Lukas Eder
- Re: jooq dsl without a connection? ericjs
- Re: jooq dsl without a connection? Sergey Epik
- Re: jooq dsl without a connection... ericjs
- Re: jooq dsl without a connec... Sergey Epik
- Re: jooq dsl without a co... Lukas Eder
- Re: jooq dsl without a co... ericjs
- Re: jooq dsl without a co... ericjs
- Re: jooq dsl without a co... ericjs
- Re: jooq dsl without a co... Lukas Eder
- Re: jooq dsl without a co... Eric Schwarzenbach
- Re: jooq dsl without a co... Eric Schwarzenbach
- Re: jooq dsl without a co... Lukas Eder
- Re: jooq dsl without a co... Lukas Eder
- Re: jooq dsl without a co... Lukas Eder
- Re: jooq dsl without a co... Lukas Eder
- Re: jooq dsl without a connection... Lukas Eder
- Re: jooq dsl without a connection? Lukas Eder
- Re: jooq dsl without a connection? Eric Schwarzenbach
