Skip to content

@Procedure returns NULL when I use parametermode.REFCursor [DATAJPA-1719] #2014

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

Closed
spring-projects-issues opened this issue May 2, 2020 · 6 comments
Assignees
Labels
type: bug A general bug

Comments

@spring-projects-issues
Copy link

pratikbhattacharya2017 opened DATAJPA-1719 and commented

You can see the example here

https://www.logicbig.com/tutorials/spring-framework/spring-data/stored-procedure-ref-cursor.html


Reference URL: https://www.logicbig.com/tutorials/spring-framework/spring-data/stored-procedure-ref-cursor.html

@spring-projects-issues
Copy link
Author

pratikbhattacharya2017 commented

Could anyone look into this. I have used weblogic as an application server, I have a road block for this

@spring-projects-issues
Copy link
Author

Jens Schauder commented

We will look into this, but there are many other thing we have to look into and therefore can't promise any response time.

In general calling stored procedures via JPA with or without Spring Data is a painful experience while at the same time not benefiting from JPA.
Given this seems to be a road block for you I suggest falling back to JDBC and Springs support classes for it (JdbcTemplate & Co)

@spring-projects-issues
Copy link
Author

pratikbhattacharya2017 commented

Thank you for the response. Can we expect any fix in upcoming release.

 

@spring-projects-issues spring-projects-issues added the type: bug A general bug label Dec 30, 2020
@gregturn gregturn self-assigned this Jul 6, 2021
gregturn pushed a commit that referenced this issue Jul 9, 2021
When registered procedure output parameters, if the method annotated with @procedure has a collection return type or an entity return type, then use ResultSet. Otherwise, handle either the array (Object[]) or the primitive types.

* Throw a proper exception when using an @Procedure-annotated method and no transaction is active.
* Introduce refCursor as a boolean flag to @procedure denoting when to use REF_CURSORs for OUT parameters..
* Extract a ProcedureParameter command object to ease usage of a parameter's name, type and mode. (NOTE: javax.persistence already has "StoredProcedureParameter".)

NOTE: Integration testing of stored procedures is very limited by lack of HSQL's support for REF CURSORS. See ##2256 to track future work for potential testing against MySQL, Oracle, Postgres, or SQL Server.

See: #1959, #409.
Related: #2014.
@gregturn
Copy link
Contributor

gregturn commented Jul 9, 2021

#1959 was recently resolved. Feel free to test out the snapshots to see if it results your issue as well.

@gregturn gregturn closed this as completed Jul 9, 2021
@gregturn gregturn reopened this Jul 9, 2021
@gregturn gregturn added the status: waiting-for-feedback We need additional information before we can continue label Jul 9, 2021
@spring-projects-issues
Copy link
Author

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.

@spring-projects-issues spring-projects-issues added the status: feedback-reminder We've sent a reminder that we need additional information before we can continue label Jul 16, 2021
@spring-projects-issues
Copy link
Author

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.

@spring-projects-issues spring-projects-issues removed status: waiting-for-feedback We need additional information before we can continue status: feedback-reminder We've sent a reminder that we need additional information before we can continue labels Jul 23, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug A general bug
Projects
None yet
Development

No branches or pull requests

3 participants