-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Postgres stored procedures not executing #2903
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
Comments
Looks like something fundamental has changed regarding stored procedures in Postgres 11+. Our current integration tests use Postgres 10, and run just fine. Back then, stored procedures were simply functions with a void return type. Apparently, this has changed massively, and considering we simply later over JPA regarding stored procedure invocations, I'm trying to glean where the real issue is. |
@Jolymmiles What version of Postgres are you using? |
If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed. |
Closing due to lack of requested feedback. If you would like us to look at this issue, please provide the requested information and we will re-open the issue. |
We know that this involves Postgres 11+. |
Postgres stored procedures requires some adjustments in order to upgrade to Postgres 11. See #2903
Postgres stored procedures requires some adjustments in order to upgrade to Postgres 11. See #2903
Postgres stored procedures requires some adjustments in order to upgrade to Postgres 11. See #2903
Because Postgres didn't have proper stored procedures in versions 10 and earlier, we had integration testing using that combined with that. However, with Postgres 11+, there is now proper support through JPA/Hibernate, etc. For stored procedures to work properly for you you can either:
|
Postgres stored procedures requires some adjustments in order to upgrade to Postgres 11. See #2903
Tests updated for |
Get errors when start stored procedure
The text was updated successfully, but these errors were encountered: