-
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
Upsert only works for PostgreSQL #1768
Comments
@DavideD upsert() works for PostgreSQL because The PG DB test creates a Other DB's create a I still don't know enough about this MutationExecutor framework to move toward a fix. |
It seems that we need to replace the |
Ah no, sorry.... I confused the two methods |
Are you sure that's the issue? Have you checked with Hibernate ORM and MySQL (for example)? I'm asking because in Hibernate ORM the implementation of Without running any code, it seems that returning |
I'll check back into ORM. thx |
@DavideD
|
The test seems correct, but I think you've copied the parameter binding from the update. The logic in ORM is quite different though, there is a Also, there are a couple of |
Pushed latest changes again to: blafond@b5ec092
|
Related to PR #1765
We added an upsert method to the stateless session interfaces in Hibernate Reactive.
For example in Mutiny.StatelessSession#upsert.
The problem is that it seems to only work for PostgreSQL.
The test fails for the other databases because when it looks for the results in the db, it returns an empty list.
I've quickly checked the same test with Hibernate ORM and MySQL, and it seems to run different queries. Probably, not all databases support the operation. But we need to look into it.
The text was updated successfully, but these errors were encountered: