i am write a simple hql

select topic,prop1,prop2 from Topic as topic
left outer join Property as prop1 on topic.topicId=prop1.itemRef
left outer join Property as prop2 on topic.topicId=prop2.itemRef
where topic.tracker=0


but it throw a error

outer or full join must be followed by path expression [select topic,prop1,prop2 from com.beaconsystem.catseye3.hibs.Topic as topic left outer join Property as prop1 on topic.topicId=prop1.itemRefleft outer join Property as prop2 on topic.topicId=prop2.itemRef]
at org.apache.struts.action.RequestProcessor.processException(RequestProcessor.java:526)
at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:467)


what does it mean? what's wrong with it

All HQL property references MUST be qualified by an alias. ie. it is ALWAYS "foo.bar", never just "bar".

If you look at the examples in the Hibernate documentation, they are all like that.

Oh, and also HQL has no ON clause in an OUTER JOIN.

oh here Property is class

that is to say

i should write it

left out join topic.property as prop1

is it

if no on clause
,how hibernate know class topic and class property join on topic.topicId=prop1.itemRef

here Topic and Property is absolute

That would be the purpose of mapping a relationship between them...

oh that is to say if i want use outer join ,i must map the relation of the in the map file,is it? otherwise i only use where clause

I am not certain whether old-style SQL joins are fully avaiable or not for use in HQL. Defintely, you could do inner joins there pretty easily just by using = between the two join properties. Outer joins were always more difficult mainly due to the fact that there was really no standard way to notate it. Actually, there was using the *= syntax, but some big DB vendors (you know who you are Oracle_) decided that there propietray syntax was better and refused to adapt to the standard.

Personally, I would say that if you need to query against a relationship or to navigate across it to go ahead and map the relationship in Hibernate. The performace is actually very good with judicious use of lazy collection and proxies...

ok thanks

now

in database

table topic

topicid topic_title
38 hql_test

table Property
propertyid item_ref item_name item_value
15 38 appendString invocation
16 38 appendFloat 99.9



my hql:

select topic,prop1,prop2 from Topic as topic,Property as prop1,Property as prop2
where topic.topicId=prop1.itemRef and topic.topicId=prop2.itemRef



show result:
topicid topic_title item_value
38 hql_test invocation invocation
38 hql_test invocation 99.9
38 hql_test 99.9 invocation
38 hql_test 99.9 99.9


but i only want one
38 hql_test invocation 99.9

why return four ?

i think i resolve it

thanks :)