I'm trying to query (hql) with an extra condition on a join but keep receiving the message:



From a simply query like:



In this query, audit is a component in

I'm 100% sure I use the latest rc1 hibernate jars (reviewed my projects settings several times).

I can see in hibernate 3.1 rc1 grammar folder that the file hql.g contains:



I know I can use filters to get extra conditions on a join, but the query I'm really concerned with (the one pasted here is a simple example) do something like:

select a from A a
left join a.bs
with bs.field = :condition
left join fetch a.bs <- filter is applied to this collection instance also, and I don't want filtering for these one.

Is there any JUnit test included with this hibernate release testing the With operator so I can try it out?

Thank you very much,

Hibernate version:
3.1 rc1
Mapping documents:
Not relevant
Code between sessionFactory.openSession() and session.close():
Not relevant
Full stack trace of any exception that occurs:
No Exception
Name and version of the database you are using:
Not Relevant
The generated SQL (show_sql=true):
Doesn't reach this point
Debug level Hibernate log excerpt:
Will post on demand.

Sure there are unit tests: org.hibernate.test.hql.AdHocOnTest

What does Hibernate print out as the version when you build the SessionFactory (check the debug log)?

Even if I'm using the latest rc1 hibernate3.jar (I open the file, check out the manifest and see



It prints 3.0.5 ! How can this be possible...

I replaced all other jars by the ones included in the 3.1 rc1 release.

I'm really confused. I'm rebuilding my project from scratch. But I know that I'm not importing the same class paths several times, etc.

It may be a problem with eclipse.. (yes, I did refresh my project...)

Anyway, thanks, you gave me a way to known for sure the hibernate's version.

Is this version (printed in log.level = debug) read from the hibernate3.jar manifest?

[/code]

No, its read from the org.hibernate.cfg.Environment class. Its a hard coded value in there...

Yup, test passed.

When you start having alot of interconnected projects in eclipse and that you need to point to a jar (in my case hibernate3.jar) to compile... In fact I had my project (from which I was running) pointing to hibernate3.jar, but this one related to another project which was pointing to an old hibernate3.jar. Well, this last jar copy was considered.

In fact I didn't look in that last project because Its a project that I have splitted.. and blablab. not needing hibernate3.jar anymore...

Thank you.

(I need to justify, I look like a newb)

It is the first time I work with 3.1 and when switching from 3.0.5 to this new version (tested with beta2 and rc1), I get an exception on the first query.

On the screen I get:



following by



If I put back hibernate3.jar 3.0.5, there's no problem.

Weird.

You have an idea?[/code]

But of course. I've only answered the same exact question 5 times already this week; I even have it memorized by now...

Hint: look at your interceptor (see I even know you are using an interceptor ;)

Thank you lord, thank you Jesus!

I'm sorry I ask silly question, but the point is that I have to be code complete in 1h for a release.

I replaced



by



Yippie ;)

Just extend org.hibernate.EmptyInterceptor and just override the methods you care about; that way you isolate yourself from furture additions

Done.

Thanks again. You saved me.