-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Improvements to clarify type using TypedParameterValue
#2370
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
Labels
type: enhancement
A general enhancement
Comments
I'd also like to see this happen very soon if possible, as otherwise we need to work around it large scale... :-( See https://hibernate.atlassian.net/browse/HHH-14411 for more details... |
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When using a native query, null value binding behaves differently depending on the SQL driver.
(For example, I faced the following issue with hibernate + postgres combination. - https://hibernate.atlassian.net/browse/HHH-14778)
But since we know the type when we write methods in
JpaRepository
, we can useTypedParameterValue
(or otherwise) to clearly know the type of the parameter.This issue is derived from #2366.
The text was updated successfully, but these errors were encountered: