It seems that it is not possible to use the @Where annotation when mapping a collection of entities that make use of the JOIN inheritance strategy. The problem is that Hibernate assumes that the column referenced in the @Where clause will be found in the table of the entity we are limiting, rather than also checking for the column in the super-class tables for that entity.

I have created a Jira issue and a test case demonstrating the problem: https://hibernate.atlassian.net/browse/HHH-12016

My question is if anyone can think of a workaround for this problem. How can I limit my @OneToMany children, without giving up inheritance?

There is a workaround.

Just use @JoinFormula on the @ManyToOne association.

Vlad, could you please expand a little on your answer?

I already tried using @JoinFormula, but the problem I ran into was that Hibernate generated a sub-select query inside the outter join condition, resulting in error. So that didn't work either.

It is possible that I used @JoinFormula wrong though. Could you please show me how to do it correctly? The details of what I tried are here:
https://stackoverflow.com/questions/465 ... nheritance

But to summarize, I did:


What is the correct way to do it?

Just make the @ManyToOne LAZY. By default, it's EAGER, which is bad for performance and it's not working for you either.

If I make it LAZY, does it not just defer exactly the same problem until the time when I do want to fetch the latest ApplicationProjectVersion? Besides, I never want the Application w/o the latest ApplicationProjectVersion - it's not useful w/o it.

If you defer it, it will use a secondary query.

If you always need it, then just remove the complex relationship and write a JPQL/SQL query to fetch these two using a JOIN instead. Usually, an exotic association is a code smell.

Just to follow up, I did end up discovering a way to emulate a polymorphic @Where annotation.

Solution described here:
https://stackoverflow.com/questions/465 ... nheritance