-
Notifications
You must be signed in to change notification settings - Fork 92
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
Simplify identity generation #1553
Milestone
Comments
DavideD
added a commit
to DavideD/hibernate-reactive
that referenced
this issue
Apr 3, 2023
This property might make sense with JDBC. But the Vert.x client is less flexible about the type of queries it needs to read the id.
DavideD
added a commit
to DavideD/hibernate-reactive
that referenced
this issue
Apr 3, 2023
DavideD
added a commit
to DavideD/hibernate-reactive
that referenced
this issue
Apr 3, 2023
DavideD
added a commit
that referenced
this issue
Apr 3, 2023
This property might make sense with JDBC. But the Vert.x client is less flexible about the type of queries it needs to read the id.
DavideD
added a commit
that referenced
this issue
Apr 3, 2023
DavideD
added a commit
that referenced
this issue
Apr 3, 2023
Done |
We are using the query generated when the property is set to false. Some of the related issues we've created on ORM: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
JDBC can generate an identity using different strategies. One can tell Hibernate ORM which one to choose using
hibernate.jdbc.use_get_generated_keys
. Currently, we are trying to support all the queries generated by Hibernate ORM for the different cases.With the Vert.x client, we usually have one way to get the id, so we can ignore the property and select the best option for each database.
The text was updated successfully, but these errors were encountered: