Skip to content

Execution of derived stored procedures fails if named parameters are used [DATAJPA-681] #1058

@spring-projects-issues

Description

@spring-projects-issues

Oliver Drotbohm opened DATAJPA-681 and commented

If a derived stored procedure is used (like here in the Spring Data examples) and named parameters are enabled (e.g., through compiling with -parameters on JDK 8) the execution fails as the output parameter will always be bound by position. This effectively means mixing named and positional parameters which is forbidden by the JPA spec.

We should alter newAdhocStoredProcedureQuery() by using a synthetic output parameter name if named parameters are used


Affects: 1.6.5 (Dijkstra SR5), 1.7.2 (Evans SR2)

Referenced from: commits spring-projects/spring-data-examples@797db3e

Backported to: 1.7.3 (Evans SR3), 1.6.6 (Dijkstra SR6)

Metadata

Metadata

Assignees

Labels

in: coreIssues in core supporttype: bugA general bug

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions