-
Notifications
You must be signed in to change notification settings - Fork 40.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Auto-configure jOOQ with R2DBC #30760
Comments
Recent jOOQ 3.x releases require Java 11 which makes upgraded problematic in 2.x where we have a Java 8 baseline. We may be able to look at this in 3.x. |
Since Springboot 3 has java 17 as base maybe it's time to relook |
jOOQ 3.18.0 is aligned with R2dbc 1.0 spec which is compatible with Spring Boot 3.x now, it is time to add R2dbc/Jooq Autoconfiguration. |
Is there any update this issue? |
@giger85 No, I'm afraid not. We work in the open so updates will appear in this issue when we have them. Right now, the issue is in the 3.x milestone. This means that we hope to work on it for a 3.x release but do not know when that will be. We have other, higher priority, items to focus on at the moment. |
I have used jOOQ and R2dbc in a project for over one year, it is easy to integrate them in projects yourself. Just need to create a But unfortunately, the Spring tx, R2dbc context mapping, etc are not applied to jOOQ SQL execution. Our strategy is only using jOOQ for complex query(across multiple tables, Db built-in functions, etc.), all create/update/delete and simple query operations use the existing Spring Data R2dbc. |
Hi @wilkinsona , I guess it is time to check in 3.3 as we are starting new journey from today |
Jooq added official R2dbc support since 3.15 , see: https://blog.jooq.org/reactive-sql-with-jooq-3-15-and-r2dbc/
Add JooqAutoConfiguration for R2dbc support, including compatibility with the existing transaction, data types, converters etc.
The text was updated successfully, but these errors were encountered: