HQL query "where exists (subquery)" fails

[gregturn]

The following query:

select u 
from UserAccountEntity u
join fetch u.lossInspectorLimitConfiguration lil
join fetch u.companyTeam ct
where exists (
	select iu 
	from UserAccountEntity  iu
	join iu.roles u2r
	join u2r.role r
	join r.rights r2r
	join r2r.right rt
	where 
		rt.code = :rightCode
		and iu = u   
)
and ct.id = :teamId

...while valid according to the official HQL parser, doesn't pass validation with Spring Data JPA.

[gregturn]

Related: #2322 (comment)

[gregturn]

Problem appears to be that RIGHT is commented out as a reserved word. (https://github.com/spring-projects/spring-data-jpa/blob/main/spring-data-jpa/src/main/antlr4/org/springframework/data/jpa/repository/query/Hql.g4#L776)

Need to uncomment it out so that it will roll up as an identifier and let the rest of the query parse.

[gregturn]

A query like this:

select u
from UserAccountEntity u
join fetch u.lossInspectorLimitConfiguration lil
join fetch u.companyTeam ct
where exists (
	select iu
	from UserAccountEntity  iu
	join iu.roles u2r
	join u2r.role r
	join r.rights r2r
	join r2r.right rt
	where
		rt.code = :rightCode
		and iu = u
)
and ct.id = :teamId

...will fail because RIGHT is recognized as a token but NOT as a potential identifier. Thus is breaks the query. By including it in the list of reserved words, which are then rolled up under identifier, it's possible for this query to work correctly.

Consequently, the other reserved words, which were originally commented out as well, should ALSO be uncommented and tested as well.