Encountering it here too. Maybe if createCriteria() and createAlias() could be coded to avoid duplicating the aliases/association paths and just graft the criterion onto the existing paths?

All the other workarounds we've considered smell bad...

I encountered the same issue but found a solution for my case at least. If your problem is the same as mine could you not just add an alias? i.e



I found this solution on page 265 of "Hibernate in Action"

I really don't understand what Hibernate is complaining about.

What is the problem with the query?

the problem is that hibernate does not appear to support self-joins correctly, which means that Criteria queries cannot be used for a whole host of query types that require multiple self-joins, such as graph matching. i don't see why not, because the difference between joining a table to itself or to another table seems like a trivial implementation issue...

perhaps a developer could shed enough light on the code limitation preventing this feature so that one of us could implement a fix, or at least comment on the status of this bug?

[edit: double post]

Any update on that limitation ? We are also quite struck over here.

Thanks !

I though I was just doing something wrong until I came across this.

This seems to be such a fundamental issue and makes a many to one relationship almost pointless in any instance where you need to control which of the one you return based on the many (via criteria).

Just in case I am doing something silly though, say I have the following.

I have a table that maps A's to B's, so if A 1 maps to B 5, 6, 7, 8 and 9 I have

A | B
------
1 | 5
1 | 6
1 | 7
1 | 8
1 | 9

Currently using criteria I can return A where B is in (5, 6, 7, 8, 9) hence I can return A where any of my B's map to it.

However if I want only those where A maps to all the B's in my list I can't do it through a criteria since I would need a join/alias from A to B for each eq clause.

(Note - this is only a small part of a programatically built up criteria set that effectively implements a configurable search function. As such taking this case in isolation does not solve the issue, it has to be 'plugable' into a larger criteria set)

What is the status of this issue, it's over a year since last post.

Cheers,
Steinard.

I have been running into this limitation many times the last decade so i figured
it would help others to know the only practical workaround i have found so far :
Just map the same association as many times as you need to join it

so Cat would get two collections : kittens0 and kittens1
then :

does work as intended.

It's but ugly, i know and does puts a limitation on how many time one may join the association
So maybe it could get patched into the criteria API in order to make it transparent to the user...