HQL fails silently when using = null

Hibernate ORM
1

Hello,
I have noticed that when I use HQL checking for a null I must now use is null. eg

tradingEol is null

generated sql:

 where
        cd1_0.isenabled=1 
        and wd1_0.updateTime>? 
        and wd1_0.tradingEol is null 
        and chcdo1_0.periodplus3>0

rather than
tradingEol = null

generated sql:

 where
        cd1_0.isenabled=1 
        and wd1_0.updateTime>? 
        and wd1_0.tradingEol=null 
        and chcdo1_0.periodplus3>0

There is no warning and just fails silently. Checking the generated sql is seems to fail on the joins (there is no join info logged).

I am using 6.4.2.

Is this intentional?

Cheers

2

This is intentional as it aligns with how SQL works. Also read up on this here: hibernate-orm/migration-guide.adoc at 6.3 · hibernate/hibernate-orm · GitHub

3

OK thanks, thought I would check. Just got to find them now in my code!

Cheers.