- I have a folder of db migration scripts
- Flyway runs them all on an h2 database in Postgres mode, then dumps the
- There's a gradle task that makes sure that the db migrations -> schema
mapping is always up-to-date
- I'd like to slurp this schema into an h2 in Postgres mode, and use that
to generate code with jOOQ.
The problem is, jOOQ barfs when generating code against the h2 db in
Postgres mode. Here's the jOOQ config:
version = '3.9.5'
edition = 'OSS'
name = 'org.jooq.util.DefaultGenerator'
driver = 'org.h2.Driver'
url = 'jdbc:h2:mem:;MODE=PostgreSQL;INIT=runscript from
Thank you very much for your suggestion. Indeed, the overhead of creating
an intermediary Record should be avoided. The main reason why it currently
cannot is because of the RecordListener SPI semantics, which guarantees
that any Record ever fetched by jOOQ passes through this SPI. The
fetchResultSet() method that you're mentioning is breaking this assumption.
The new default behaviour will be to bypass intermediary Record types if no
RecordListeners are registered in the Configuration. There are quite a few
API methods that can then be optimised for most users.
Right now, I'm afraid you have to resort to writing your own utility to get
the ResultSetMapper semantics.
You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page.
To unsubscribe from this group and stop receiving emails from it send an email to [hidden email].