Fix NEGATING_SIMPLE_PROPERTY to use IS NOT NULL when argument is null #3681
+5
−2
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.
When a query method uses NEGATING_SIMPLE_PROPERTY and the argument is null, the generated query should now use
IS NOT NULL
instead of<>
. This ensures consistent behavior when handling null values across queries.Changes:
JpaQueryCreator
to handle null arguments inNEGATING_SIMPLE_PROPERTY
by rewriting<>
toIS NOT NULL
.Closes #3675