Repository navigation
HHH-20955 Fix reuse of binding parameter across several attributes - #13704
Open
HiMyNameIsIlNano wants to merge 1 commit into
Open
HiMyNameIsIlNano wants to merge 1 commit into
HiMyNameIsIlNano wants to merge 1 commit into
Conversation
|
Thanks for your pull request! This pull request appears to follow the contribution rules. › This message was automatically generated. |
…aring an AttributeConverter A JPQL query that compares several entity attributes against one single named parameter fails to bind when the attributes are mapped with the same @convert(converter = ...), whose relational type is not one of the types BindingTypeHelper.resolveTimestampTemporalTypeVariant knows, and the parameter is used three or more times across at least two different such attributes.
HiMyNameIsIlNano
force-pushed
the
HHH-20955
branch
from
October 16, 2026 13:46
b441230 to
23235c9
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fix reuse of binding parameter across several attributes sharing an AttributeConverter
A JPQL query that compares several entity attributes against one single named parameter fails to bind when the attributes are mapped with the same @convert(converter = ...), whose relational type is not one of the types BindingTypeHelper.resolveTimestampTemporalTypeVariant knows, and the parameter is used three or more times across at least two different such attributes.
Here we have a two-steps issue. The QueryParameterBindingImpl#setType re-checks on each further use of a parameter within a query whether the new attribute is compatible with the previous one, and bails out to NullType when it is not. The compatibility check compares value converters by reference identity (i.e. using ==). So four attributes carrying the very same converter class end up with four distinct converter instances . This way two structurally identical attributes are judged incompatible, and Hibernate drops the inferred type (binding it to NullType).
Once this is done (and the binding is NullType) JdbcParameterBindings#createAndAddBinding resolves the type by the value runtime class. As the AttributeConverter has already done its job at that point, the OffsetDateTime has become a LocalDateTime, and BindingTypeHelper#resolveTimestampTemporalTypeVariant throws an error not being able to handle LocalDateTime (allowed values are Calendar, java.util.Date, Instant, OffsetDateTime, ZonedDateTime).
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license
and can be relicensed under the terms of the LGPL v2.1 license in the future at the maintainers' discretion.
For more information on licensing, please check here.
Please make sure that the following tasks are completed:
Tasks specific to HHH-20955 (Bug):
migration-guide.adocOR check there are no breaking changeshttps://hibernate.atlassian.net/browse/HHH-20955