[Hibernate-JIRA] Created: (HHH-2739) 'illegal attempt to dereference collection' when referencing a single-valued association in an implicit join
10 p.m.
'illegal attempt to dereference collection' when referencing a single-valued
association in an implicit join
------------------------------------------------------------------------------------------------------------
Key: HHH-2739
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2739
Project: Hibernate3
Issue Type: Bug
Affects Versions: 3.2.4.sp1, 3.2.4, 3.2.3
Environment: I have found that behaviour in version 3.2.4.sp1 and 3.2.3 (I
didn't test 3.2.4 pre sp1)
Database: ORACLE 10g
Reporter: Martin Kouba
After upgrading to the latest Hibernate version I got this error.
I try to use a statement like this
from cat c where c.mate.id = 13
the expected resulting SQL should be something like
SELECT * FROM CAT C WHERE C.MATE_ID = 13
which is much more performant than making a join
from cat c join c.mate m where m.id = 13
which would result in something like that
SELECT * FROM CAT C INNER JOIN MATE M ON C.MATE_ID = M.ID WHERE M.ID = 13
This works as expected in 3.1.3, 3.2.0 and 3.2.2
It doesn't work with version 3.2.3 and with 3.2.4.sp1.
As test case you can take the example from the documentation chapter 5.1.16
<?xml version="1.0"?>
<!DOCTYPE hibernate-mapping PUBLIC
"-//Hibernate/Hibernate Mapping DTD//EN"
"http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd">
<hibernate-mapping package="eg">
<class name="Cat" table="CATS">
<id name="id" column="uid"
type="long">
<generator class="hilo"/>
</id>
<property name="birthdate" type="date"/>
<property name="color" not-null="true"/>
<property name="sex" not-null="true"/>
<property name="weight"/>
<many-to-one name="mate"/>
<set name="kittens">
<key column="MOTHER"/>
<one-to-many class="Cat"/>
</set>
<joined-subclass name="DomesticCat"
table="DOMESTIC_CATS">
<key column="CAT"/>
<property name="name" type="string"/>
</joined-subclass>
</class>
<class name="eg.Dog">
<!-- mapping for Dog could go here -->
</class>
</hibernate-mapping>
c = new Cat();
c.setMate(new Cat());
c.persist();
int id = c.getId();
List results = session.createQuery("from Cat as c where c.mate.id = 16).list();
according to manual section 14.5 this should work
http://www.hibernate.org/hib_docs/v3/reference/en/html_single/#queryhql-i...
Ok, I hope this is clear enough and the test case is clear enough as well.
This is a major stopper for an upgrade. I have reported that on June 11th
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2667
But it seems that others used the same case to report a similar issue regarding automatic
joins.
According to Christian Bauer automatic joins are no longer supported, closed the case and
told me to reopen it again.
So to all others please do not add comments to this case if it is not about it. And to the
Hibernate developers: Greate work you are doing but please I think the issue was clear
when I reported it the first time. It is quite easy to reproduce and occurs quite often in
a medium size project.
Gratitude
Martin
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:06 a.m.
New subject: [Hibernate-JIRA] Closed: (HHH-2739) 'illegal attempt to dereference collection' when referencing a single-valued association in an implicit join
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2739?page=c...
]
Steve Ebersole closed HHH-2739.
-------------------------------
Resolution: Fixed
You mean something along the lines of:
public void testIt() {
Session s = sf.openSession();
System.out.println( "to-one dereference
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~" );
s.createQuery( "from Cat c where c.mate.color = 'black'" );
System.out.println(
"~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~" );
System.out.println( "to-many dereference
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~" );
s.createQuery( "from Cat where c.kittens.color = 'black'" );
System.out.println(
"~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~" );
s.close();
}
With output like:
to-one dereference ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
to-many dereference ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
org.hibernate.QueryException: illegal attempt to dereference collection
[cat0_.uid.kittens] with element property reference [color] [from Cat c where
c.kittens.color = 'black']
at
org.hibernate.hql.ast.tree.DotNode$1.buildIllegalCollectionDereferenceException(DotNode.java:46)
at org.hibernate.hql.ast.tree.DotNode.checkLhsIsNotCollection(DotNode.java:512)
at org.hibernate.hql.ast.tree.DotNode.resolve(DotNode.java:221)
at org.hibernate.hql.ast.tree.FromReferenceNode.resolve(FromReferenceNode.java:94)
at org.hibernate.hql.ast.tree.FromReferenceNode.resolve(FromReferenceNode.java:90)
at org.hibernate.hql.ast.HqlSqlWalker.resolve(HqlSqlWalker.java:728)
at org.hibernate.hql.antlr.HqlSqlBaseWalker.expr(HqlSqlBaseWalker.java:1216)
at org.hibernate.hql.antlr.HqlSqlBaseWalker.exprOrSubquery(HqlSqlBaseWalker.java:4041)
at org.hibernate.hql.antlr.HqlSqlBaseWalker.comparisonExpr(HqlSqlBaseWalker.java:3525)
at org.hibernate.hql.antlr.HqlSqlBaseWalker.logicalExpr(HqlSqlBaseWalker.java:1762)
at org.hibernate.hql.antlr.HqlSqlBaseWalker.whereClause(HqlSqlBaseWalker.java:776)
at org.hibernate.hql.antlr.HqlSqlBaseWalker.query(HqlSqlBaseWalker.java:577)
at org.hibernate.hql.antlr.HqlSqlBaseWalker.selectStatement(HqlSqlBaseWalker.java:281)
at org.hibernate.hql.antlr.HqlSqlBaseWalker.statement(HqlSqlBaseWalker.java:229)
at org.hibernate.hql.ast.QueryTranslatorImpl.analyze(QueryTranslatorImpl.java:228)
at org.hibernate.hql.ast.QueryTranslatorImpl.doCompile(QueryTranslatorImpl.java:160)
at org.hibernate.hql.ast.QueryTranslatorImpl.compile(QueryTranslatorImpl.java:111)
at org.hibernate.engine.query.HQLQueryPlan.<init>(HQLQueryPlan.java:77)
at org.hibernate.engine.query.HQLQueryPlan.<init>(HQLQueryPlan.java:56)
at org.hibernate.engine.query.QueryPlanCache.getHQLQueryPlan(QueryPlanCache.java:72)
at org.hibernate.impl.AbstractSessionImpl.getHQLQueryPlan(AbstractSessionImpl.java:133)
at org.hibernate.impl.AbstractSessionImpl.createQuery(AbstractSessionImpl.java:112)
at org.hibernate.impl.SessionImpl.createQuery(SessionImpl.java:1623)
at Test.testIt(Test.java:49)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:40)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at com.intellij.rt.execution.application.AppMain.main(AppMain.java:90)
???
'illegal attempt to dereference collection' when referencing
a single-valued association in an implicit join
------------------------------------------------------------------------------------------------------------
Key: HHH-2739
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2739
Project: Hibernate3
Issue Type: Bug
Affects Versions: 3.2.3, 3.2.4, 3.2.4.sp1
Environment: I have found that behaviour in version 3.2.4.sp1 and 3.2.3 (I
didn't test 3.2.4 pre sp1)
Database: ORACLE 10g
Reporter: Martin Kouba
After upgrading to the latest Hibernate version I got this error.
I try to use a statement like this
from cat c where c.mate.id = 13
the expected resulting SQL should be something like
SELECT * FROM CAT C WHERE C.MATE_ID = 13
which is much more performant than making a join
from cat c join c.mate m where m.id = 13
which would result in something like that
SELECT * FROM CAT C INNER JOIN MATE M ON C.MATE_ID = M.ID WHERE M.ID = 13
This works as expected in 3.1.3, 3.2.0 and 3.2.2
It doesn't work with version 3.2.3 and with 3.2.4.sp1.
As test case you can take the example from the documentation chapter 5.1.16
<?xml version="1.0"?>
<!DOCTYPE hibernate-mapping PUBLIC
"-//Hibernate/Hibernate Mapping DTD//EN"
"http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd">
<hibernate-mapping package="eg">
<class name="Cat" table="CATS">
<id name="id" column="uid"
type="long">
<generator class="hilo"/>
</id>
<property name="birthdate" type="date"/>
<property name="color" not-null="true"/>
<property name="sex" not-null="true"/>
<property name="weight"/>
<many-to-one name="mate"/>
<set name="kittens">
<key column="MOTHER"/>
<one-to-many class="Cat"/>
</set>
<joined-subclass name="DomesticCat"
table="DOMESTIC_CATS">
<key column="CAT"/>
<property name="name" type="string"/>
</joined-subclass>
</class>
<class name="eg.Dog">
<!-- mapping for Dog could go here -->
</class>
</hibernate-mapping>
c = new Cat();
c.setMate(new Cat());
c.persist();
int id = c.getId();
List results = session.createQuery("from Cat as c where c.mate.id = 16).list();
according to manual section 14.5 this should work
http://www.hibernate.org/hib_docs/v3/reference/en/html_single/#queryhql-i...
Ok, I hope this is clear enough and the test case is clear enough as well.
This is a major stopper for an upgrade. I have reported that on June 11th
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2667
But it seems that others used the same case to report a similar issue regarding automatic
joins.
According to Christian Bauer automatic joins are no longer supported, closed the case and
told me to reopen it again.
So to all others please do not add comments to this case if it is not about it. And to
the Hibernate developers: Greate work you are doing but please I think the issue was clear
when I reported it the first time. It is quite easy to reproduce and occurs quite often in
a medium size project.
Gratitude
Martin
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:23 p.m.
New subject: [Hibernate-JIRA] Closed: (HHH-2739) 'illegal attempt to dereference collection' when referencing a single-valued association in an implicit join
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2739?page=c...
]
Steve Ebersole closed HHH-2739.
-------------------------------
Assignee: Steve Ebersole
Resolution: Cannot Reproduce
'illegal attempt to dereference collection' when referencing
a single-valued association in an implicit join
------------------------------------------------------------------------------------------------------------
Key: HHH-2739
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2739
Project: Hibernate3
Issue Type: Bug
Affects Versions: 3.2.3, 3.2.4, 3.2.4.sp1
Environment: I have found that behaviour in version 3.2.4.sp1 and 3.2.3 (I
didn't test 3.2.4 pre sp1)
Database: ORACLE 10g
Reporter: Martin Kouba
Assignee: Steve Ebersole
After upgrading to the latest Hibernate version I got this error.
I try to use a statement like this
from cat c where c.mate.id = 13
the expected resulting SQL should be something like
SELECT * FROM CAT C WHERE C.MATE_ID = 13
which is much more performant than making a join
from cat c join c.mate m where m.id = 13
which would result in something like that
SELECT * FROM CAT C INNER JOIN MATE M ON C.MATE_ID = M.ID WHERE M.ID = 13
This works as expected in 3.1.3, 3.2.0 and 3.2.2
It doesn't work with version 3.2.3 and with 3.2.4.sp1.
As test case you can take the example from the documentation chapter 5.1.16
<?xml version="1.0"?>
<!DOCTYPE hibernate-mapping PUBLIC
"-//Hibernate/Hibernate Mapping DTD//EN"
"http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd">
<hibernate-mapping package="eg">
<class name="Cat" table="CATS">
<id name="id" column="uid"
type="long">
<generator class="hilo"/>
</id>
<property name="birthdate" type="date"/>
<property name="color" not-null="true"/>
<property name="sex" not-null="true"/>
<property name="weight"/>
<many-to-one name="mate"/>
<set name="kittens">
<key column="MOTHER"/>
<one-to-many class="Cat"/>
</set>
<joined-subclass name="DomesticCat"
table="DOMESTIC_CATS">
<key column="CAT"/>
<property name="name" type="string"/>
</joined-subclass>
</class>
<class name="eg.Dog">
<!-- mapping for Dog could go here -->
</class>
</hibernate-mapping>
c = new Cat();
c.setMate(new Cat());
c.persist();
int id = c.getId();
List results = session.createQuery("from Cat as c where c.mate.id = 16).list();
according to manual section 14.5 this should work
http://www.hibernate.org/hib_docs/v3/reference/en/html_single/#queryhql-i...
Ok, I hope this is clear enough and the test case is clear enough as well.
This is a major stopper for an upgrade. I have reported that on June 11th
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2667
But it seems that others used the same case to report a similar issue regarding automatic
joins.
According to Christian Bauer automatic joins are no longer supported, closed the case and
told me to reopen it again.
So to all others please do not add comments to this case if it is not about it. And to
the Hibernate developers: Greate work you are doing but please I think the issue was clear
when I reported it the first time. It is quite easy to reproduce and occurs quite often in
a medium size project.
Gratitude
Martin
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:23 p.m.
New subject: [Hibernate-JIRA] Reopened: (HHH-2739) 'illegal attempt to dereference collection' when referencing a single-valued association in an implicit join
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2739?page=c...
]
Steve Ebersole reopened HHH-2739:
---------------------------------
'illegal attempt to dereference collection' when referencing
a single-valued association in an implicit join
------------------------------------------------------------------------------------------------------------
Key: HHH-2739
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2739
Project: Hibernate3
Issue Type: Bug
Affects Versions: 3.2.3, 3.2.4, 3.2.4.sp1
Environment: I have found that behaviour in version 3.2.4.sp1 and 3.2.3 (I
didn't test 3.2.4 pre sp1)
Database: ORACLE 10g
Reporter: Martin Kouba
After upgrading to the latest Hibernate version I got this error.
I try to use a statement like this
from cat c where c.mate.id = 13
the expected resulting SQL should be something like
SELECT * FROM CAT C WHERE C.MATE_ID = 13
which is much more performant than making a join
from cat c join c.mate m where m.id = 13
which would result in something like that
SELECT * FROM CAT C INNER JOIN MATE M ON C.MATE_ID = M.ID WHERE M.ID = 13
This works as expected in 3.1.3, 3.2.0 and 3.2.2
It doesn't work with version 3.2.3 and with 3.2.4.sp1.
As test case you can take the example from the documentation chapter 5.1.16
<?xml version="1.0"?>
<!DOCTYPE hibernate-mapping PUBLIC
"-//Hibernate/Hibernate Mapping DTD//EN"
"http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd">
<hibernate-mapping package="eg">
<class name="Cat" table="CATS">
<id name="id" column="uid"
type="long">
<generator class="hilo"/>
</id>
<property name="birthdate" type="date"/>
<property name="color" not-null="true"/>
<property name="sex" not-null="true"/>
<property name="weight"/>
<many-to-one name="mate"/>
<set name="kittens">
<key column="MOTHER"/>
<one-to-many class="Cat"/>
</set>
<joined-subclass name="DomesticCat"
table="DOMESTIC_CATS">
<key column="CAT"/>
<property name="name" type="string"/>
</joined-subclass>
</class>
<class name="eg.Dog">
<!-- mapping for Dog could go here -->
</class>
</hibernate-mapping>
c = new Cat();
c.setMate(new Cat());
c.persist();
int id = c.getId();
List results = session.createQuery("from Cat as c where c.mate.id = 16).list();
according to manual section 14.5 this should work
http://www.hibernate.org/hib_docs/v3/reference/en/html_single/#queryhql-i...
Ok, I hope this is clear enough and the test case is clear enough as well.
This is a major stopper for an upgrade. I have reported that on June 11th
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2667
But it seems that others used the same case to report a similar issue regarding automatic
joins.
According to Christian Bauer automatic joins are no longer supported, closed the case and
told me to reopen it again.
So to all others please do not add comments to this case if it is not about it. And to
the Hibernate developers: Greate work you are doing but please I think the issue was clear
when I reported it the first time. It is quite easy to reproduce and occurs quite often in
a medium size project.
Gratitude
Martin
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:05 p.m.
New subject: [Hibernate-JIRA] Commented: (HHH-2739) 'illegal attempt to dereference collection' when referencing a single-valued association in an implicit join
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2739?page=c...
]
Steve Ebersole commented on HHH-2739:
-------------------------------------
Oh and in case there are further complaints about not using .id to derefernence the
many-to-one, here is the result of that:
public void testIdReferenceShortcut() {
Session s = sf.openSession();
s.createQuery( "from Cat c where c.mate.id = 123" ).list();
s.close();
}
which produces:
Hibernate:
select
cat0_.uid as uid0_,
cat0_.birthdate as birthdate0_,
cat0_.color as color0_,
cat0_.sex as sex0_,
cat0_.weight as weight0_,
cat0_.mate as mate0_,
cat0_1_.name as name1_,
case
when cat0_1_.CAT is not null then 1
when cat0_.uid is not null then 0
end as clazz_
from
CATS cat0_
left outer join
DOMESTIC_CATS cat0_1_
on cat0_.uid=cat0_1_.CAT
where
cat0_.mate=123
Note that the join here has nothing to do with the hql restriction, it is related to the
subclassing.
'illegal attempt to dereference collection' when referencing
a single-valued association in an implicit join
------------------------------------------------------------------------------------------------------------
Key: HHH-2739
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2739
Project: Hibernate3
Issue Type: Bug
Affects Versions: 3.2.3, 3.2.4, 3.2.4.sp1
Environment: I have found that behaviour in version 3.2.4.sp1 and 3.2.3 (I
didn't test 3.2.4 pre sp1)
Database: ORACLE 10g
Reporter: Martin Kouba
Assignee: Steve Ebersole
After upgrading to the latest Hibernate version I got this error.
I try to use a statement like this
from cat c where c.mate.id = 13
the expected resulting SQL should be something like
SELECT * FROM CAT C WHERE C.MATE_ID = 13
which is much more performant than making a join
from cat c join c.mate m where m.id = 13
which would result in something like that
SELECT * FROM CAT C INNER JOIN MATE M ON C.MATE_ID = M.ID WHERE M.ID = 13
This works as expected in 3.1.3, 3.2.0 and 3.2.2
It doesn't work with version 3.2.3 and with 3.2.4.sp1.
As test case you can take the example from the documentation chapter 5.1.16
<?xml version="1.0"?>
<!DOCTYPE hibernate-mapping PUBLIC
"-//Hibernate/Hibernate Mapping DTD//EN"
"http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd">
<hibernate-mapping package="eg">
<class name="Cat" table="CATS">
<id name="id" column="uid"
type="long">
<generator class="hilo"/>
</id>
<property name="birthdate" type="date"/>
<property name="color" not-null="true"/>
<property name="sex" not-null="true"/>
<property name="weight"/>
<many-to-one name="mate"/>
<set name="kittens">
<key column="MOTHER"/>
<one-to-many class="Cat"/>
</set>
<joined-subclass name="DomesticCat"
table="DOMESTIC_CATS">
<key column="CAT"/>
<property name="name" type="string"/>
</joined-subclass>
</class>
<class name="eg.Dog">
<!-- mapping for Dog could go here -->
</class>
</hibernate-mapping>
c = new Cat();
c.setMate(new Cat());
c.persist();
int id = c.getId();
List results = session.createQuery("from Cat as c where c.mate.id = 16).list();
according to manual section 14.5 this should work
http://www.hibernate.org/hib_docs/v3/reference/en/html_single/#queryhql-i...
Ok, I hope this is clear enough and the test case is clear enough as well.
This is a major stopper for an upgrade. I have reported that on June 11th
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2667
But it seems that others used the same case to report a similar issue regarding automatic
joins.
According to Christian Bauer automatic joins are no longer supported, closed the case and
told me to reopen it again.
So to all others please do not add comments to this case if it is not about it. And to
the Hibernate developers: Greate work you are doing but please I think the issue was clear
when I reported it the first time. It is quite easy to reproduce and occurs quite often in
a medium size project.
Gratitude
Martin
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:03 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-2739) 'illegal attempt to dereference collection' when referencing a single-valued association in an implicit join
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2739?page=c...
]
Gilliard Santos Cordeiro commented on HHH-2739:
-----------------------------------------------
I have the same problem with Hibernate 3.2.5.ga
'illegal attempt to dereference collection' when referencing
a single-valued association in an implicit join
------------------------------------------------------------------------------------------------------------
Key: HHH-2739
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2739
Project: Hibernate3
Issue Type: Bug
Affects Versions: 3.2.3, 3.2.4, 3.2.4.sp1
Environment: I have found that behaviour in version 3.2.4.sp1 and 3.2.3 (I
didn't test 3.2.4 pre sp1)
Database: ORACLE 10g
Reporter: Martin Kouba
Assignee: Steve Ebersole
After upgrading to the latest Hibernate version I got this error.
I try to use a statement like this
from cat c where c.mate.id = 13
the expected resulting SQL should be something like
SELECT * FROM CAT C WHERE C.MATE_ID = 13
which is much more performant than making a join
from cat c join c.mate m where m.id = 13
which would result in something like that
SELECT * FROM CAT C INNER JOIN MATE M ON C.MATE_ID = M.ID WHERE M.ID = 13
This works as expected in 3.1.3, 3.2.0 and 3.2.2
It doesn't work with version 3.2.3 and with 3.2.4.sp1.
As test case you can take the example from the documentation chapter 5.1.16
<?xml version="1.0"?>
<!DOCTYPE hibernate-mapping PUBLIC
"-//Hibernate/Hibernate Mapping DTD//EN"
"http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd">
<hibernate-mapping package="eg">
<class name="Cat" table="CATS">
<id name="id" column="uid"
type="long">
<generator class="hilo"/>
</id>
<property name="birthdate" type="date"/>
<property name="color" not-null="true"/>
<property name="sex" not-null="true"/>
<property name="weight"/>
<many-to-one name="mate"/>
<set name="kittens">
<key column="MOTHER"/>
<one-to-many class="Cat"/>
</set>
<joined-subclass name="DomesticCat"
table="DOMESTIC_CATS">
<key column="CAT"/>
<property name="name" type="string"/>
</joined-subclass>
</class>
<class name="eg.Dog">
<!-- mapping for Dog could go here -->
</class>
</hibernate-mapping>
c = new Cat();
c.setMate(new Cat());
c.persist();
int id = c.getId();
List results = session.createQuery("from Cat as c where c.mate.id = 16).list();
according to manual section 14.5 this should work
http://www.hibernate.org/hib_docs/v3/reference/en/html_single/#queryhql-i...
Ok, I hope this is clear enough and the test case is clear enough as well.
This is a major stopper for an upgrade. I have reported that on June 11th
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2667
But it seems that others used the same case to report a similar issue regarding automatic
joins.
According to Christian Bauer automatic joins are no longer supported, closed the case and
told me to reopen it again.
So to all others please do not add comments to this case if it is not about it. And to
the Hibernate developers: Greate work you are doing but please I think the issue was clear
when I reported it the first time. It is quite easy to reproduce and occurs quite often in
a medium size project.
Gratitude
Martin
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:13 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-2739) 'illegal attempt to dereference collection' when referencing a single-valued association in an implicit join
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2739?page=c...
]
Yoon Kyung Koo commented on HHH-2739:
-------------------------------------
I have the same problem with 3.2.3ga or 3.2.5ga. In 3.1.3 and below, it worked fine.
Please, re-open this issue.
'illegal attempt to dereference collection' when referencing
a single-valued association in an implicit join
------------------------------------------------------------------------------------------------------------
Key: HHH-2739
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2739
Project: Hibernate3
Issue Type: Bug
Affects Versions: 3.2.3, 3.2.4, 3.2.4.sp1
Environment: I have found that behaviour in version 3.2.4.sp1 and 3.2.3 (I
didn't test 3.2.4 pre sp1)
Database: ORACLE 10g
Reporter: Martin Kouba
Assignee: Steve Ebersole
After upgrading to the latest Hibernate version I got this error.
I try to use a statement like this
from cat c where c.mate.id = 13
the expected resulting SQL should be something like
SELECT * FROM CAT C WHERE C.MATE_ID = 13
which is much more performant than making a join
from cat c join c.mate m where m.id = 13
which would result in something like that
SELECT * FROM CAT C INNER JOIN MATE M ON C.MATE_ID = M.ID WHERE M.ID = 13
This works as expected in 3.1.3, 3.2.0 and 3.2.2
It doesn't work with version 3.2.3 and with 3.2.4.sp1.
As test case you can take the example from the documentation chapter 5.1.16
<?xml version="1.0"?>
<!DOCTYPE hibernate-mapping PUBLIC
"-//Hibernate/Hibernate Mapping DTD//EN"
"http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd">
<hibernate-mapping package="eg">
<class name="Cat" table="CATS">
<id name="id" column="uid"
type="long">
<generator class="hilo"/>
</id>
<property name="birthdate" type="date"/>
<property name="color" not-null="true"/>
<property name="sex" not-null="true"/>
<property name="weight"/>
<many-to-one name="mate"/>
<set name="kittens">
<key column="MOTHER"/>
<one-to-many class="Cat"/>
</set>
<joined-subclass name="DomesticCat"
table="DOMESTIC_CATS">
<key column="CAT"/>
<property name="name" type="string"/>
</joined-subclass>
</class>
<class name="eg.Dog">
<!-- mapping for Dog could go here -->
</class>
</hibernate-mapping>
c = new Cat();
c.setMate(new Cat());
c.persist();
int id = c.getId();
List results = session.createQuery("from Cat as c where c.mate.id = 16).list();
according to manual section 14.5 this should work
http://www.hibernate.org/hib_docs/v3/reference/en/html_single/#queryhql-i...
Ok, I hope this is clear enough and the test case is clear enough as well.
This is a major stopper for an upgrade. I have reported that on June 11th
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2667
But it seems that others used the same case to report a similar issue regarding automatic
joins.
According to Christian Bauer automatic joins are no longer supported, closed the case and
told me to reopen it again.
So to all others please do not add comments to this case if it is not about it. And to
the Hibernate developers: Greate work you are doing but please I think the issue was clear
when I reported it the first time. It is quite easy to reproduce and occurs quite often in
a medium size project.
Gratitude
Martin
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:37 p.m.
New subject: [Hibernate-JIRA] Commented: (HHH-2739) 'illegal attempt to dereference collection' when referencing a single-valued association in an implicit join
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2739?page=c...
]
Diego Pires Plentz commented on HHH-2739:
-----------------------------------------
If you want to re-open this issue, attach a runnable testcase (java+mapping), and if you
have a solution, the patch.
'illegal attempt to dereference collection' when referencing
a single-valued association in an implicit join
------------------------------------------------------------------------------------------------------------
Key: HHH-2739
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2739
Project: Hibernate3
Issue Type: Bug
Affects Versions: 3.2.3, 3.2.4, 3.2.4.sp1
Environment: I have found that behaviour in version 3.2.4.sp1 and 3.2.3 (I
didn't test 3.2.4 pre sp1)
Database: ORACLE 10g
Reporter: Martin Kouba
Assignee: Steve Ebersole
After upgrading to the latest Hibernate version I got this error.
I try to use a statement like this
from cat c where c.mate.id = 13
the expected resulting SQL should be something like
SELECT * FROM CAT C WHERE C.MATE_ID = 13
which is much more performant than making a join
from cat c join c.mate m where m.id = 13
which would result in something like that
SELECT * FROM CAT C INNER JOIN MATE M ON C.MATE_ID = M.ID WHERE M.ID = 13
This works as expected in 3.1.3, 3.2.0 and 3.2.2
It doesn't work with version 3.2.3 and with 3.2.4.sp1.
As test case you can take the example from the documentation chapter 5.1.16
<?xml version="1.0"?>
<!DOCTYPE hibernate-mapping PUBLIC
"-//Hibernate/Hibernate Mapping DTD//EN"
"http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd">
<hibernate-mapping package="eg">
<class name="Cat" table="CATS">
<id name="id" column="uid"
type="long">
<generator class="hilo"/>
</id>
<property name="birthdate" type="date"/>
<property name="color" not-null="true"/>
<property name="sex" not-null="true"/>
<property name="weight"/>
<many-to-one name="mate"/>
<set name="kittens">
<key column="MOTHER"/>
<one-to-many class="Cat"/>
</set>
<joined-subclass name="DomesticCat"
table="DOMESTIC_CATS">
<key column="CAT"/>
<property name="name" type="string"/>
</joined-subclass>
</class>
<class name="eg.Dog">
<!-- mapping for Dog could go here -->
</class>
</hibernate-mapping>
c = new Cat();
c.setMate(new Cat());
c.persist();
int id = c.getId();
List results = session.createQuery("from Cat as c where c.mate.id = 16).list();
according to manual section 14.5 this should work
http://www.hibernate.org/hib_docs/v3/reference/en/html_single/#queryhql-i...
Ok, I hope this is clear enough and the test case is clear enough as well.
This is a major stopper for an upgrade. I have reported that on June 11th
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2667
But it seems that others used the same case to report a similar issue regarding automatic
joins.
According to Christian Bauer automatic joins are no longer supported, closed the case and
told me to reopen it again.
So to all others please do not add comments to this case if it is not about it. And to
the Hibernate developers: Greate work you are doing but please I think the issue was clear
when I reported it the first time. It is quite easy to reproduce and occurs quite often in
a medium size project.
Gratitude
Martin
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:19 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-2739) 'illegal attempt to dereference collection' when referencing a single-valued association in an implicit join
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2739?page=c...
]
Yoon Kyung Koo commented on HHH-2739:
-------------------------------------
I found this is a duplication of 2667. I resolved the problem by the guide of Nick Folder.
Just copying that ...
---
Nick Folder - [22/Jul/07 04:00 PM ]
From the Hibernate 3.2 Migration Guide:
"Query language changes
Implicit joins are more deterministic
With such mapping:
<class name='Currency' lazy='false'>
....
</class>
<class name='Asset'>
<id name='id' ... </id>
<many-to-one name='currency' class='Currency'
fetch='select'/>
</class>
and such HQL query:
select a.id, a.currency from Asset a
Since Hibernate 3.2.2 this query generates an inner join on Asset with Currency which
means that Assets with a NULL currency are not returned by the query anymore.
This makes implicit joins more deterministic.
To get Assets with a NULL currency just use
select a.id, c from Asset a left join a.currency as c
Path expressions joining across a collection throw exception
The always illegal statement:
select f.bars.baz from Foo f
Now throws an exception. Despite the always present warning in the documentation that this
is an illegal path expression if bars is a collection, users found this to be working in
some cases with Hibernate 3.1. This is no longer the case, an error is thrown. As always,
the correct syntax is an explicit join:
select b.baz from Foo f join f.bars b"
'illegal attempt to dereference collection' when referencing
a single-valued association in an implicit join
------------------------------------------------------------------------------------------------------------
Key: HHH-2739
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2739
Project: Hibernate3
Issue Type: Bug
Affects Versions: 3.2.3, 3.2.4, 3.2.4.sp1
Environment: I have found that behaviour in version 3.2.4.sp1 and 3.2.3 (I
didn't test 3.2.4 pre sp1)
Database: ORACLE 10g
Reporter: Martin Kouba
Assignee: Steve Ebersole
After upgrading to the latest Hibernate version I got this error.
I try to use a statement like this
from cat c where c.mate.id = 13
the expected resulting SQL should be something like
SELECT * FROM CAT C WHERE C.MATE_ID = 13
which is much more performant than making a join
from cat c join c.mate m where m.id = 13
which would result in something like that
SELECT * FROM CAT C INNER JOIN MATE M ON C.MATE_ID = M.ID WHERE M.ID = 13
This works as expected in 3.1.3, 3.2.0 and 3.2.2
It doesn't work with version 3.2.3 and with 3.2.4.sp1.
As test case you can take the example from the documentation chapter 5.1.16
<?xml version="1.0"?>
<!DOCTYPE hibernate-mapping PUBLIC
"-//Hibernate/Hibernate Mapping DTD//EN"
"http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd">
<hibernate-mapping package="eg">
<class name="Cat" table="CATS">
<id name="id" column="uid"
type="long">
<generator class="hilo"/>
</id>
<property name="birthdate" type="date"/>
<property name="color" not-null="true"/>
<property name="sex" not-null="true"/>
<property name="weight"/>
<many-to-one name="mate"/>
<set name="kittens">
<key column="MOTHER"/>
<one-to-many class="Cat"/>
</set>
<joined-subclass name="DomesticCat"
table="DOMESTIC_CATS">
<key column="CAT"/>
<property name="name" type="string"/>
</joined-subclass>
</class>
<class name="eg.Dog">
<!-- mapping for Dog could go here -->
</class>
</hibernate-mapping>
c = new Cat();
c.setMate(new Cat());
c.persist();
int id = c.getId();
List results = session.createQuery("from Cat as c where c.mate.id = 16).list();
according to manual section 14.5 this should work
http://www.hibernate.org/hib_docs/v3/reference/en/html_single/#queryhql-i...
Ok, I hope this is clear enough and the test case is clear enough as well.
This is a major stopper for an upgrade. I have reported that on June 11th
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2667
But it seems that others used the same case to report a similar issue regarding automatic
joins.
According to Christian Bauer automatic joins are no longer supported, closed the case and
told me to reopen it again.
So to all others please do not add comments to this case if it is not about it. And to
the Hibernate developers: Greate work you are doing but please I think the issue was clear
when I reported it the first time. It is quite easy to reproduce and occurs quite often in
a medium size project.
Gratitude
Martin
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6228
days inactive
6369
days old
hibernate-issues@lists.jboss.org
8 comments
5 participants
participants (5)
-
Diego Pires Plentz (JIRA) -
Gilliard Santos Cordeiro (JIRA)
-
Martin Kouba (JIRA)
-
Steve Ebersole (JIRA)
-
Yoon Kyung Koo (JIRA)