You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With #541 (DATAJPA-121), we introduced a long time ago rewrite from foo = ? to foo IS NULL if the query method argument yields null. We should consistently rewrite its negating form from foo <> ? to foo IS NOT NULL if the query method argument is null.
The text was updated successfully, but these errors were encountered:
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:
- Updated `JpaQueryCreator` to handle null arguments in `NEGATING_SIMPLE_PROPERTY` by rewriting `<>` to `IS NOT NULL`.
Closesspring-projects#3675
bezzang-dev
added a commit
to bezzang-dev/spring-data-jpa
that referenced
this issue
Nov 15, 2024
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:
- Updated `JpaQueryCreator` to handle null arguments in `NEGATING_SIMPLE_PROPERTY` by rewriting `<>` to `IS NOT NULL`.
Closesspring-projects#3675
With #541 (DATAJPA-121), we introduced a long time ago rewrite from
foo = ?
tofoo IS NULL
if the query method argument yieldsnull
. We should consistently rewrite its negating form fromfoo <> ?
tofoo IS NOT NULL
if the query method argument isnull
.The text was updated successfully, but these errors were encountered: