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

Procedure with one output parameter [DATAJPA-1442] #1759

Closed
spring-projects-issues opened this issue Oct 16, 2018 · 0 comments
Closed

Procedure with one output parameter [DATAJPA-1442] #1759

spring-projects-issues opened this issue Oct 16, 2018 · 0 comments
Assignees
Labels
in: core Issues in core support type: bug A general bug

Comments

@spring-projects-issues
Copy link

Carlos Orellana Bermejo opened DATAJPA-1442 and commented

Creating a procedure like:

@NamedStoredProcedureQuery(name = "get_error_db" , procedureName = "DB_NAME", parameters = {
@StoredProcedureParameter(mode = ParameterMode.OUT, name = "P_ERROR", type = String.class)

and doing the calling:

@Procedure(name = "get_error_db")
String getErrorDB();

 

i got this error:

Invalid mix of named and positional parameters; nested exception is java.lang.IllegalArgumentException: Invalid mix of named and positional parameters

 

For resolving this error I deleted the name of the parameter P_ERROR in the procedure creation. I don't know if this is a bug or this is the normal method of doing this type of query


Affects: 2.1.1 (Lovelace SR1)

@spring-projects-issues spring-projects-issues added type: bug A general bug in: core Issues in core support labels Dec 30, 2020
@mp911de mp911de assigned mp911de and unassigned odrotbohm Oct 21, 2024
mp911de added a commit that referenced this issue Oct 21, 2024
Refine stored procedure documentation.

See #1759
mp911de added a commit that referenced this issue Oct 21, 2024
We assume that if a stored procedure is named (associated with the Persitence Context) that we can access its out values by name.

Closes #1759
mp911de added a commit that referenced this issue Oct 21, 2024
Refine stored procedure documentation.

See #1759
mp911de added a commit that referenced this issue Oct 21, 2024
Refine stored procedure documentation.

See #1759
mp911de added a commit that referenced this issue Oct 21, 2024
We assume that if a stored procedure is named (associated with the Persitence Context) that we can access its out values by name.

Closes #1759
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: core Issues in core support type: bug A general bug
Projects
None yet
Development

No branches or pull requests

3 participants