-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Revise TypedParameterValue
usage for native queries only
#3137
Comments
sxhinzvc
added a commit
that referenced
this issue
Sep 25, 2023
Use Hibernate parameter accessor for native queries only to avoid affecting JPA queries. See #3137
sxhinzvc
added a commit
that referenced
this issue
Sep 25, 2023
Use Hibernate parameter accessor for native queries only to avoid affecting JPQL queries. See #3137
mp911de
pushed a commit
that referenced
this issue
Sep 27, 2023
Use Hibernate parameter accessor for native queries only to avoid affecting JPQL queries. Co-locate Hibernate-specific parameters accessor as the same package as JPA parameters accessor. Remove Parameter Accessor reference from Persistence Provider since it's created in AbstractJpaQuery. Closes #3137 Original Pull Request: #3173
mp911de
pushed a commit
that referenced
this issue
Sep 27, 2023
Use Hibernate parameter accessor for native queries only to avoid affecting JPQL queries. Co-locate Hibernate-specific parameters accessor as the same package as JPA parameters accessor. Remove Parameter Accessor reference from Persistence Provider since it's created in AbstractJpaQuery. Closes #3137 Original Pull Request: #3173
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As per discussion in #3060,
TypedParameterValue
should be used for native queries only. UsingTypedParameterValue
with JPQL/HQL queries conflicts with the JPQL typing and can cause that@Convert
ers are not considered.The text was updated successfully, but these errors were encountered: