Skip to content
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

Closed
DavideD opened this issue Apr 3, 2023 · 2 comments
Closed

Simplify identity generation #1553

DavideD opened this issue Apr 3, 2023 · 2 comments
Assignees
Milestone

Comments

@DavideD
Copy link
Member

DavideD commented Apr 3, 2023

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.

@DavideD DavideD self-assigned this Apr 3, 2023
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 DavideD added this to the next milestone Apr 5, 2023
@DavideD
Copy link
Member Author

DavideD commented Apr 5, 2023

Done

@DavideD DavideD closed this as completed Apr 5, 2023
@DavideD
Copy link
Member Author

DavideD commented Apr 5, 2023

We are using the query generated when the property is set to false.
We are having a couple of issues with the queries generated by ORM that we will need to investigate if we want to remove the additional operations we do on the generated queries here.

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
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant