jooq

Im currently accessing an embedded H2 database in java using jOOQ to generate table classes etc. I can currently execute queries such as create.select().from(TEST).fetch() in my code, return results etc. However I cant query the information schema. I can access it ok using the H2 console, and creating a view for a given information_schema table works fine. My question is how should I be accessing the information_schema eg to perform a query such as SELECT * FROM INFORMATION_SCHEMA.TABLES from within my java code? Do I have to create a view, can the schema be accessed through jooq-meta or some

Based on comments in https://www.jooq.org/doc/3.6/manual/sql-execution/transaction-management/ changing isolation level doesn't seems possible with Jooq yet. However it is not clear what is the isolation level Jooq is setting, hence my question: what is the isolation level that Jooq is using? Especially, it looks like I am experiencing dirty reads, while I need the transaction to prevent that. Can someone confirm that dirty reads are prevented by Jooq transactions? Note: Using Jooq with Mysql. The DB is an AWS Aurora instance. jOOQ 3.9 doesn't support managing transaction isolation levels yet.

I have 2 similar schemas in simple database - "develop" and "stage". I have generated Java classes with Jooq for one of that schemas ("develop" for example). When jooq generates query to db, it implicitly add schema's name to all query's aliases select "develop"."image"."id", "develop"."image"."image_data" from "develop"."image" where "develop"."image"."id" = ? So my question is, whether there are the way to change jooq schema name (for "stage" as an example) in generated query without regenerating jooq's classes for "stage" schema? You have several options, which can even be combined: Use the

Does jOOQ provide support for JSR310 in combination with PostgreSQL? In particular, I am trying to use the following classes: java.time.Instant java.time.LocalDate java.time.LocalTime java.time.LocalDateTime I am storing in the following data types (as per http://www.postgresql.org/docs/9.1/static/datatype-datetime.html ): java.time.Instant : timestamp with timezone java.time.LocalDate : date java.time.LocalTime : time without timezone java.time.LocalDateTime : timestamp without timezone Are these data types correct? Does jOOQ support translation between java.sql.Timestamp , java.sql.Date and

This question already has an answer here: Troubleshoot slow compilation 3 answers The following bug was reported to the jOOQ user group . It really seems to be a bug in the javac compiler related to rather "complex" type inference work done by the compiler in the context of using an internal DSL like jOOQ is. Given the general nature of the bug, I'm documenting it here on Stack Overflow for others to help apply workarounds if they run into it. On a high level, it seems to be a compiler performance regression due to JEP 101: Generalized Target-Type Inference , which was introduced in Java 8 and