[Hibernate-JIRA] Created: (HHH-5526) Dirty Entity instances in session after HQL queries with where conditions on OneToMany relation
10:31 a.m.
Dirty Entity instances in session after HQL queries with where conditions on OneToMany
relation
-----------------------------------------------------------------------------------------------
Key: HHH-5526
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5526
Project: Hibernate Core
Issue Type: Bug
Components: core, query-hql
Affects Versions: 3.3.2
Environment: Hibernate 3.3.2.GA, Java 1.6
Reporter: Felix von Delius
Having a OneToMany relation on Team.persons, after you execute a HQL query in the form
"select distinct t from Team t join fetch t.persons p where p.id = ?"
the selected Team instance only contains the one person with the id searched for (i.e.
missing other persons in this team).
Probably this could be worked around by changing the query, the main problem ist that this
broken Team instance is attached in the session and querying for the team by it's id
returns this broken team:
Team newTeamFetchedById = session.get(Team.class, TEAM_ID); // team id from the query
above
Evicting the fetched team and repeating the query again fetches a team with the correct
number of persons.
--
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
4:51 p.m.
New subject: [Hibernate-JIRA] Resolved: (HHH-5526) Dirty Entity instances in session after HQL queries with where conditions on OneToMany relation
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5526?page=c...
]
Gail Badner resolved HHH-5526.
------------------------------
Assignee: Gail Badner
Resolution: Rejected
This is expected behavior.
Dirty Entity instances in session after HQL queries with where
conditions on OneToMany relation
-----------------------------------------------------------------------------------------------
Key: HHH-5526
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5526
Project: Hibernate Core
Issue Type: Bug
Components: core, query-hql
Affects Versions: 3.3.2
Environment: Hibernate 3.3.2.GA, Java 1.6
Reporter: Felix von Delius
Assignee: Gail Badner
Having a OneToMany relation on Team.persons, after you execute a HQL query in the form
"select distinct t from Team t join fetch t.persons p where p.id = ?"
the selected Team instance only contains the one person with the id searched for (i.e.
missing other persons in this team).
Probably this could be worked around by changing the query, the main problem ist that
this broken Team instance is attached in the session and querying for the team by it's
id returns this broken team:
Team newTeamFetchedById = session.get(Team.class, TEAM_ID); // team id from the query
above
Evicting the fetched team and repeating the query again fetches a team with the correct
number of persons.
--
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:58 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-5526) Dirty Entity instances in session after HQL queries with where conditions on OneToMany relation
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5526?page=c...
]
Felix von Delius commented on HHH-5526:
---------------------------------------
This is expected behavior.
Huh? When executing a query that starts with "select from Team t join fetch
t.persons", I would expect to get the team with *all* it's members, independent
of the where clause. And even if this is a idiosyncrasy of this specific query, executing
another query in the same session where the team is selected by id, I would expect to get
the complete team.
Btw: leaving out the "fetch" in the above query seems to return the team with
all members.
If this is really the correct, expected behaviour, where is this "expected"
behaviour documented?
Executing the same query as a criteria query does have the (IMHO) expected behaviour
(returning the team with all it's members):
Criteria crit = session.createCriteria(Team.class);
crit.createAlias("persons", "p");
crit.add(Restrictions.eq("p.id", teamMember.getId()));
List<Person> teamList = crit.list();
Dirty Entity instances in session after HQL queries with where
conditions on OneToMany relation
-----------------------------------------------------------------------------------------------
Key: HHH-5526
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5526
Project: Hibernate Core
Issue Type: Bug
Components: core, query-hql
Affects Versions: 3.3.2
Environment: Hibernate 3.3.2.GA, Java 1.6
Reporter: Felix von Delius
Assignee: Gail Badner
Having a OneToMany relation on Team.persons, after you execute a HQL query in the form
"select distinct t from Team t join fetch t.persons p where p.id = ?"
the selected Team instance only contains the one person with the id searched for (i.e.
missing other persons in this team).
Probably this could be worked around by changing the query, the main problem ist that
this broken Team instance is attached in the session and querying for the team by it's
id returns this broken team:
Team newTeamFetchedById = session.get(Team.class, TEAM_ID); // team id from the query
above
Evicting the fetched team and repeating the query again fetches a team with the correct
number of persons.
--
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:09 a.m.
New subject: [Hibernate-JIRA] Issue Comment Edited: (HHH-5526) Dirty Entity instances in session after HQL queries with where conditions on OneToMany relation
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5526?page=c...
]
Felix von Delius edited comment on HHH-5526 at 9/16/10 3:09 AM:
----------------------------------------------------------------
This is expected behavior.
Huh? When executing a query that starts with "select from Team t join fetch
t.persons", I would expect to get the team with *all* it's members, independent
of the where clause. And even if this is a idiosyncrasy of this specific query, executing
another query in the same session where the team is selected by id, I would expect to get
the complete team.
Btw: leaving out the "fetch" in the above query seems to return the team with
all members.
If this is really the correct, expected behaviour, where is this "expected"
behaviour documented?
Executing the same query as a criteria query does have the (IMHO) expected behaviour
(returning the team with all it's members):
Criteria crit = session.createCriteria(Team.class);
crit.createAlias("persons", "p");
crit.add(Restrictions.eq("p.id", teamMember.getId()));
List<Team> teamList = crit.list();
was (Author: fvdiba):
This is expected behavior.
Huh? When executing a query that starts with "select from Team t join fetch
t.persons", I would expect to get the team with *all* it's members, independent
of the where clause. And even if this is a idiosyncrasy of this specific query, executing
another query in the same session where the team is selected by id, I would expect to get
the complete team.
Btw: leaving out the "fetch" in the above query seems to return the team with
all members.
If this is really the correct, expected behaviour, where is this "expected"
behaviour documented?
Executing the same query as a criteria query does have the (IMHO) expected behaviour
(returning the team with all it's members):
Criteria crit = session.createCriteria(Team.class);
crit.createAlias("persons", "p");
crit.add(Restrictions.eq("p.id", teamMember.getId()));
List<Person> teamList = crit.list();
Dirty Entity instances in session after HQL queries with where
conditions on OneToMany relation
-----------------------------------------------------------------------------------------------
Key: HHH-5526
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5526
Project: Hibernate Core
Issue Type: Bug
Components: core, query-hql
Affects Versions: 3.3.2
Environment: Hibernate 3.3.2.GA, Java 1.6
Reporter: Felix von Delius
Assignee: Gail Badner
Having a OneToMany relation on Team.persons, after you execute a HQL query in the form
"select distinct t from Team t join fetch t.persons p where p.id = ?"
the selected Team instance only contains the one person with the id searched for (i.e.
missing other persons in this team).
Probably this could be worked around by changing the query, the main problem ist that
this broken Team instance is attached in the session and querying for the team by it's
id returns this broken team:
Team newTeamFetchedById = session.get(Team.class, TEAM_ID); // team id from the query
above
Evicting the fetched team and repeating the query again fetches a team with the correct
number of persons.
--
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
4998
days inactive
5012
days old
hibernate-issues@lists.jboss.org
3 comments
2 participants
participants (2)
-
Felix von Delius (JIRA) -
Gail Badner (JIRA)