Using Hibernate 2.1.2 here.

Briefly, the object I am querying for is a Document. It has a Metadata object, which contains a HashMap called 'data'. 'data' maps field names to AbstractMetadataValue objects.

The following query works and returns the desired object:



It gives me the Documents that have a metadata value named 'description' that contains the string 'desc'.

However, the same query does not work within an inner select statement like this:



I get the following stack trace, which appears to indicate that this syntax is not supported. Is there a reason why this query does not work? It seems like it ought to.

[/quote][/code]

It's been a number of months since I posted the original question in this thread and I've now come back to where the workaround I implemented is really bothering me. We are now using Hibernate 2.1.8 and the problem persists.

So I did some debugging in the Hibernate source and found out why the WhereParser class is throwing an exception when it sees the '[' character inside of the inner select query. The details (as I see them) are posted below.

I modified the code just to test out my theory and indeed the problem was fixed. My question is should I post a potential patch or is Hibernate 2.1.X dead and should I just switch over to Hibernate 3.0 and hope that the problem is fixed there?

More details available upon request, I just didn't want to overdo it here if it wasn't really necessary.

Thanks

----------------------

Details:

The token() method in WhereParser just builds up a String containing the text within the parens that mark the inner query. It then constructs a new QueryTranslator to parse that string.

When the original query parser hits that [, it should ignore it because it's part of the inner select, which is going to be handled later by the 2nd query parser. But it doesn't. It sees that the bracket is out of place and throws an exception.

My proposed fix is to wrap the lines dealing with path continuations within a conditional to ensure that we're not in a sub select. The fix appeared to work (it solved my problem) and the unit tests ran successfully.