Hi, thanks for the testcase.

I’ve been looking at this today and it’s indeed a special case which we should fix, but I suspect this is rather something we should do in Hibernate ORM 6.

Sorry it will have to wait a bit, but the workaround is easy: change the property name if you need to use such HQL functions.