Compile with parameter names #1513
Labels
type: task
A general task
Milestone
Comments
mp911de
changed the title
mp911de
added a commit
that referenced
this issue
Sep 7, 2021
mp911de
added a commit
that referenced
this issue
Sep 7, 2021
mp911de
added a commit
to spring-projects/spring-data-jpa
that referenced
this issue
Sep 14, 2021
We now no longer use compiled parameter names for tests to avoid interference with Eclipselink's mechanism of using these improperly for stored procedure calls. Especially the fact that a parameter is named "in" lets the database consider using an IN clause instead of the parameter name. When configuring the compile plugin, we also need to ensure that the AspectJ plugin post-processes the compiled classes and doesn't run before the Maven compiler plugin. Closes: #2298 See also spring-projects/spring-data-build#1513
mp911de
added a commit
to spring-projects/spring-data-jpa
that referenced
this issue
Sep 14, 2021
We now no longer use compiled parameter names for tests to avoid interference with Eclipselink's mechanism of using these improperly for stored procedure calls. Especially the fact that a parameter is named "in" lets the database consider using an IN clause instead of the parameter name. When configuring the compile plugin, we also need to ensure that the AspectJ plugin post-processes the compiled classes and doesn't run before the Maven compiler plugin. Closes: #2298 See also spring-projects/spring-data-build#1513
mp911de
added a commit
to spring-projects/spring-data-jpa
that referenced
this issue
Sep 14, 2021
We now no longer use compiled parameter names for tests to avoid interference with Eclipselink's mechanism of using these improperly for stored procedure calls. Especially the fact that a parameter is named "in" lets the database consider using an IN clause instead of the parameter name. When configuring the compile plugin, we also need to ensure that the AspectJ plugin post-processes the compiled classes and doesn't run before the Maven compiler plugin. Closes: #2298 See also spring-projects/spring-data-build#1513
trayanus1026
pushed a commit
to trayanus1026/spring-data-jpa-java
that referenced
this issue
Aug 5, 2023
We now no longer use compiled parameter names for tests to avoid interference with Eclipselink's mechanism of using these improperly for stored procedure calls. Especially the fact that a parameter is named "in" lets the database consider using an IN clause instead of the parameter name. When configuring the compile plugin, we also need to ensure that the AspectJ plugin post-processes the compiled classes and doesn't run before the Maven compiler plugin. Closes: #2298 See also spring-projects/spring-data-build#1513
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Compiled code should contain parameter names to avoid the need for resources to be included in native image builds.
The text was updated successfully, but these errors were encountered: