10:41 a.m.
fetch="join" and property-ref
-----------------------------
Key: HHH-2473
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2473
Project: Hibernate3
Type: Improvement
Versions: 3.2.1
Environment: Version 3.2.1, not DB dependant
Reporter: David CLEMENT
When Hibernate does a fetch join with a property-ref in a many-to-one, it issues the join
SQL query but needs another select to find the associated entity by property-ref.
It should be able to use the entity fetched in the join instead (maybe this has been done
to ensure the unicity of the associated entity, but it introduce a performance issue).
--
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
9:17 p.m.
New subject: [Hibernate-JIRA] Commented: (HHH-2473) fetch="join" and property-ref
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2473?page=c...
]
Bill Swayze commented on HHH-2473:
----------------------------------
I am experiencing a similar problem in HQL with many-to-one associations using a
property-ref. The 'one' end of the association is retrieved and partially
resolved and saved in entitiesByKey. In subsequent result set processing, an attempt to
resolve the entity in entitiesByUniqueKey is unsuccessful as it is trying to use the pk.
Ultimately, the entity is null in the results of .list().
Consider the following mappings and query:
<?xml version="1.0"?>
<!DOCTYPE hibernate-mapping PUBLIC
"-//Hibernate/Hibernate Mapping DTD 2.0//EN"
"http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd" >
<hibernate-mapping>
<class name="test.A"
table="a_t">
<id name="id" column="id" type="java.lang.Integer">
<generator class="assigned"/>
</id>
<many-to-one name="child" class="test.B"
column="str_id" property-ref="key" not-null="true"/>
</class>
</hibernate-mapping>
<?xml version="1.0"?>
<!DOCTYPE hibernate-mapping PUBLIC
"-//Hibernate/Hibernate Mapping DTD 2.0//EN"
"http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd" >
<hibernate-mapping>
<class name="test.B"
table="b_t">
<id name="id" column="id" type="java.lang.Integer">
<generator class="assigned"/>
</id>
<property name="data" type="java.lang.String"
column="data" not-null="true" length="80" />
<property name="key" type="java.lang.String"
column="str_id" unique="true" not-null="true"
length="80" />
</class>
</hibernate-mapping>
select aa.id, bb from A aa inner join aa.child bb where aa.id = 1
fetch="join" and property-ref
-----------------------------
Key: HHH-2473
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2473
Project: Hibernate3
Issue Type: Improvement
Affects Versions: 3.2.1
Environment: Version 3.2.1, not DB dependant
Reporter: David CLEMENT
When Hibernate does a fetch join with a property-ref in a many-to-one, it issues the
join SQL query but needs another select to find the associated entity by property-ref.
It should be able to use the entity fetched in the join instead (maybe this has been done
to ensure the unicity of the associated entity, but it introduce a performance issue).
--
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
7:11 p.m.
New subject: [Hibernate-JIRA] Commented: (HHH-2473) fetch="join" and property-ref
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2473?page=c...
]
FATEC commented on HHH-2473:
----------------------------
I'm getting the same problem that DAVID reported. Please, help us.
fetch="join" and property-ref
-----------------------------
Key: HHH-2473
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2473
Project: Hibernate3
Issue Type: Improvement
Affects Versions: 3.2.1
Environment: Version 3.2.1, not DB dependant
Reporter: David CLEMENT
When Hibernate does a fetch join with a property-ref in a many-to-one, it issues the
join SQL query but needs another select to find the associated entity by property-ref.
It should be able to use the entity fetched in the join instead (maybe this has been done
to ensure the unicity of the associated entity, but it introduce a performance issue).
--
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
7:15 p.m.
New subject: [Hibernate-JIRA] Updated: (HHH-2473) fetch="join" and property-ref
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2473?page=c...
]
Christian Bauer updated HHH-2473:
---------------------------------
Comment: was deleted
fetch="join" and property-ref
-----------------------------
Key: HHH-2473
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2473
Project: Hibernate3
Issue Type: Improvement
Affects Versions: 3.2.1
Environment: Version 3.2.1, not DB dependant
Reporter: David CLEMENT
When Hibernate does a fetch join with a property-ref in a many-to-one, it issues the
join SQL query but needs another select to find the associated entity by property-ref.
It should be able to use the entity fetched in the join instead (maybe this has been done
to ensure the unicity of the associated entity, but it introduce a performance issue).
--
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
9:07 p.m.
New subject: [Hibernate-JIRA] Commented: (HHH-2473) fetch="join" and property-ref
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2473?page=c...
]
FATEC commented on HHH-2473:
----------------------------
sorry to comment again, but this is a big problem in our project, because hibernate does N
selects instead of only 1 select
when this bug will be fixed ?
thanks
fetch="join" and property-ref
-----------------------------
Key: HHH-2473
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2473
Project: Hibernate3
Issue Type: Improvement
Affects Versions: 3.2.1
Environment: Version 3.2.1, not DB dependant
Reporter: David CLEMENT
When Hibernate does a fetch join with a property-ref in a many-to-one, it issues the
join SQL query but needs another select to find the associated entity by property-ref.
It should be able to use the entity fetched in the join instead (maybe this has been done
to ensure the unicity of the associated entity, but it introduce a performance issue).
--
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
9:34 p.m.
New subject: [Hibernate-JIRA] Updated: (HHH-2473) fetch="join" and property-ref
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2473?page=c...
]
Christian Bauer updated HHH-2473:
---------------------------------
Comment: was deleted
fetch="join" and property-ref
-----------------------------
Key: HHH-2473
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2473
Project: Hibernate3
Issue Type: Improvement
Affects Versions: 3.2.1
Environment: Version 3.2.1, not DB dependant
Reporter: David CLEMENT
When Hibernate does a fetch join with a property-ref in a many-to-one, it issues the
join SQL query but needs another select to find the associated entity by property-ref.
It should be able to use the entity fetched in the join instead (maybe this has been done
to ensure the unicity of the associated entity, but it introduce a performance issue).
--
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
9:26 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-2473) fetch="join" and property-ref
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2473?page=c...
]
Trygve Amundsen commented on HHH-2473:
--------------------------------------
It seems like the superflous SQL is issued only when the fetch join returns no row.
fetch="join" and property-ref
-----------------------------
Key: HHH-2473
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2473
Project: Hibernate3
Issue Type: Improvement
Affects Versions: 3.2.1
Environment: Version 3.2.1, not DB dependant
Reporter: David CLEMENT
When Hibernate does a fetch join with a property-ref in a many-to-one, it issues the
join SQL query but needs another select to find the associated entity by property-ref.
It should be able to use the entity fetched in the join instead (maybe this has been done
to ensure the unicity of the associated entity, but it introduce a performance issue).
--
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:02 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-2473) fetch="join" and property-ref
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2473?page=c...
]
Dilip Dalton commented on HHH-2473:
-----------------------------------
This problem also occurs even if the property-ref entity is eagerly fetched. A separate
SQL is issued for each entity referred by the property-ref. This is causing performance
issues while loading the data.
Unfortunately the alternatve method of using the "foreign" id generator cannot
be used because we have existing data and the ids are not the same between the entities in
the one-to-one relationship.
So please treat this with high priority. We are even considering to completely bypass
hibernate as the performance is bad.
fetch="join" and property-ref
-----------------------------
Key: HHH-2473
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2473
Project: Hibernate3
Issue Type: Improvement
Affects Versions: 3.2.1
Environment: Version 3.2.1, not DB dependant
Reporter: David CLEMENT
When Hibernate does a fetch join with a property-ref in a many-to-one, it issues the
join SQL query but needs another select to find the associated entity by property-ref.
It should be able to use the entity fetched in the join instead (maybe this has been done
to ensure the unicity of the associated entity, but it introduce a performance issue).
--
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 p.m.
New subject: [Hibernate-JIRA] Commented: (HHH-2473) fetch="join" and property-ref
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2473?page=c...
]
Gary Sargent commented on HHH-2473:
-----------------------------------
Isn't this a bug rather than an improvement?
Hibernate should have all the data it needs as it has done the outer join to get the
entities involved. It does not need to do N selects to get the data again.
Just because property-ref is being used in the many-to-one should make no difference to
when the id is used.
This does have a bad performance implication. Can anyone from the Hibernate team comment?
fetch="join" and property-ref
-----------------------------
Key: HHH-2473
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2473
Project: Hibernate Core
Issue Type: Improvement
Affects Versions: 3.2.1
Environment: Version 3.2.1, not DB dependant
Reporter: David CLEMENT
When Hibernate does a fetch join with a property-ref in a many-to-one, it issues the
join SQL query but needs another select to find the associated entity by property-ref.
It should be able to use the entity fetched in the join instead (maybe this has been done
to ensure the unicity of the associated entity, but it introduce a performance issue).
--
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
3:49 p.m.
New subject: [Hibernate-JIRA] Commented: (HHH-2473) fetch="join" and property-ref
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2473?page=c...
]
Andrés Margalef commented on HHH-2473:
--------------------------------------
This problem also occurs in version 3.6.2.Final
fetch="join" and property-ref
-----------------------------
Key: HHH-2473
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2473
Project: Hibernate Core
Issue Type: Improvement
Affects Versions: 3.2.1
Environment: Version 3.2.1, not DB dependant
Reporter: David CLEMENT
When Hibernate does a fetch join with a property-ref in a many-to-one, it issues the
join SQL query but needs another select to find the associated entity by property-ref.
It should be able to use the entity fetched in the join instead (maybe this has been done
to ensure the unicity of the associated entity, but it introduce a performance issue).
--
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
4724
days inactive
6264
days old
hibernate-issues@lists.jboss.org
9 comments
8 participants
participants (8)
-
Andrés Margalef (JIRA) -
Bill Swayze (JIRA)
-
Christian Bauer (JIRA)
-
David CLEMENT (JIRA)
-
Dilip Dalton (JIRA)
-
FATEC (JIRA)
-
Gary Sargent (JIRA)
-
Trygve Amundsen (JIRA)