[hibernate-commits] [hibernate/hibernate-orm] de3a4c: HHH-17804 roll back change to semantics of 'null i...
Branch: refs/heads/main
Home: https://github.com/hibernate/hibernate-orm
Commit: de3a4c0af96e1a3dc23bd7aa8c7d8f5f4bcc03b8
https://github.com/hibernate/hibernate-orm/commit/de3a4c0af96e1a3dc23bd7a...
Author: Gavin King <gavin(a)hibernate.org>
Date: 2024-06-06 (Thu, 06 Jun 2024)
Changed paths:
M
hibernate-core/src/main/java/org/hibernate/persister/entity/AbstractEntityPersister.java
M hibernate-core/src/main/java/org/hibernate/sql/InFragment.java
M
hibernate-core/src/main/java/org/hibernate/sql/ast/spi/AbstractSqlAstTranslator.java
M
hibernate-core/src/test/java/org/hibernate/orm/test/jpa/criteria/basic/PredicateTest.java
Log Message:
-----------
HHH-17804 roll back change to semantics of 'null in ()'
It turns out that SQL databases (IMO wrongly) treat the expression
'null in (select 1 where false)' as false instead of null. And as
of JPA 3.2, we're free to interpret 'null in ()' consistently with
that, which we should do.
So my change made things worse rather than better.
Signed-off-by: Gavin King <gavin(a)hibernate.org>
To unsubscribe from these emails, change your notification settings at
https://github.com/hibernate/hibernate-orm/settings/notifications