[Hibernate-JIRA] Created: (HHH-5028) Calling em.remove() on child object @OneToMany relationship when CascadeType.ALL and FetchType.EAGER are set throws exception
11:41 a.m.
Calling em.remove() on child object @OneToMany relationship when CascadeType.ALL and
FetchType.EAGER are set throws exception
-----------------------------------------------------------------------------------------------------------------------------
Key: HHH-5028
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5028
Project: Hibernate Core
Issue Type: Bug
Components: entity-manager
Affects Versions: 3.5.0-CR-2
Environment: Confirmed bug using MySQL, PostgreSQL, and Hsqldb, which is what the
test is configured with. Hibernate version is 3.5.0-CR-2 (see test app pom.xml)
Reporter: Jesse Hutton
Attachments: HibernateManyToOneEagerRemove.tar.gz
Calling em.remove(foo) on the child object of a @OneToMany relationship that is defined
with CascadeType.ALL and FetchType.EAGER throws an Exception. The cause is given as:
javax.persistence.EntityNotFoundException: deleted entity passed to persist:
And all I'm doing in the test is removing an object. See attached test case.
If, however, I remove FetchType.EAGER from the @OneToMany relationship, no exception is
thrown.
--
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
5:27 p.m.
New subject: [Hibernate-JIRA] Commented: (HHH-5028) Calling em.remove() on child object @OneToMany relationship when CascadeType.ALL and FetchType.EAGER are set throws exception
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5028?page=c...
]
Gail Badner commented on HHH-5028:
----------------------------------
Is this still an issue using 3.5.1?
Calling em.remove() on child object @OneToMany relationship when
CascadeType.ALL and FetchType.EAGER are set throws exception
-----------------------------------------------------------------------------------------------------------------------------
Key: HHH-5028
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5028
Project: Hibernate Core
Issue Type: Bug
Components: entity-manager
Affects Versions: 3.5.0-CR-2
Environment: Confirmed bug using MySQL, PostgreSQL, and Hsqldb, which is what the
test is configured with. Hibernate version is 3.5.0-CR-2 (see test app pom.xml)
Reporter: Jesse Hutton
Attachments: HibernateManyToOneEagerRemove.tar.gz
Calling em.remove(foo) on the child object of a @OneToMany relationship that is defined
with CascadeType.ALL and FetchType.EAGER throws an Exception. The cause is given as:
javax.persistence.EntityNotFoundException: deleted entity passed to persist:
And all I'm doing in the test is removing an object. See attached test case.
If, however, I remove FetchType.EAGER from the @OneToMany relationship, no exception is
thrown.
--
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:43 p.m.
New subject: [Hibernate-JIRA] Commented: (HHH-5028) Calling em.remove() on child object @OneToMany relationship when CascadeType.ALL and FetchType.EAGER are set throws exception
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5028?page=c...
]
Jesse Hutton commented on HHH-5028:
-----------------------------------
Problem still exists with 3.5.1-Final. See test app (and update pom.xml to correct
version).
Calling em.remove() on child object @OneToMany relationship when
CascadeType.ALL and FetchType.EAGER are set throws exception
-----------------------------------------------------------------------------------------------------------------------------
Key: HHH-5028
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5028
Project: Hibernate Core
Issue Type: Bug
Components: entity-manager
Affects Versions: 3.5.0-CR-2
Environment: Confirmed bug using MySQL, PostgreSQL, and Hsqldb, which is what the
test is configured with. Hibernate version is 3.5.0-CR-2 (see test app pom.xml)
Reporter: Jesse Hutton
Attachments: HibernateManyToOneEagerRemove.tar.gz
Calling em.remove(foo) on the child object of a @OneToMany relationship that is defined
with CascadeType.ALL and FetchType.EAGER throws an Exception. The cause is given as:
javax.persistence.EntityNotFoundException: deleted entity passed to persist:
And all I'm doing in the test is removing an object. See attached test case.
If, however, I remove FetchType.EAGER from the @OneToMany relationship, no exception is
thrown.
--
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:57 p.m.
New subject: [Hibernate-JIRA] Updated: (HHH-5028) Calling em.remove() on child object @OneToMany relationship when CascadeType.ALL and FetchType.EAGER are set throws exception
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5028?page=c...
]
Gail Badner updated HHH-5028:
-----------------------------
Affects Version/s: 3.5.1
Calling em.remove() on child object @OneToMany relationship when
CascadeType.ALL and FetchType.EAGER are set throws exception
-----------------------------------------------------------------------------------------------------------------------------
Key: HHH-5028
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5028
Project: Hibernate Core
Issue Type: Bug
Components: entity-manager
Affects Versions: 3.5.0-CR-2, 3.5.1
Environment: Confirmed bug using MySQL, PostgreSQL, and Hsqldb, which is what the
test is configured with. Hibernate version is 3.5.0-CR-2 (see test app pom.xml)
Reporter: Jesse Hutton
Attachments: HibernateManyToOneEagerRemove.tar.gz
Calling em.remove(foo) on the child object of a @OneToMany relationship that is defined
with CascadeType.ALL and FetchType.EAGER throws an Exception. The cause is given as:
javax.persistence.EntityNotFoundException: deleted entity passed to persist:
And all I'm doing in the test is removing an object. See attached test case.
If, however, I remove FetchType.EAGER from the @OneToMany relationship, no exception is
thrown.
--
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:46 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-5028) Calling em.remove() on child object @OneToMany relationship when CascadeType.ALL and FetchType.EAGER are set throws exception
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5028?page=c...
]
Jesper Steen Møller commented on HHH-5028:
------------------------------------------
OP: What were you expecting to happen?
Since you are not removing the child from the @OneToMany collection, and since the
collection is loaded into memory, Hibernate is right to attempt to persist the child in
the (implicit) flush() operation on the parent, effectively resuscitating the child from
the remove operation. The exception is due to HHH-5124.
If the desired operation was to force the removal from the collection, you need to call
remove() on the collection. For a simple OneToMany with a mappedBy on the child, this
seems like an undesired overhead (and will work fine if the collection is not loaded), but
if the was using a join table, it would be required anyway.
Calling em.remove() on child object @OneToMany relationship when
CascadeType.ALL and FetchType.EAGER are set throws exception
-----------------------------------------------------------------------------------------------------------------------------
Key: HHH-5028
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5028
Project: Hibernate Core
Issue Type: Bug
Components: entity-manager
Affects Versions: 3.5.0-CR-2, 3.5.1
Environment: Confirmed bug using MySQL, PostgreSQL, and Hsqldb, which is what the
test is configured with. Hibernate version is 3.5.0-CR-2 (see test app pom.xml)
Reporter: Jesse Hutton
Attachments: HibernateManyToOneEagerRemove.tar.gz
Calling em.remove(foo) on the child object of a @OneToMany relationship that is defined
with CascadeType.ALL and FetchType.EAGER throws an Exception. The cause is given as:
javax.persistence.EntityNotFoundException: deleted entity passed to persist:
And all I'm doing in the test is removing an object. See attached test case.
If, however, I remove FetchType.EAGER from the @OneToMany relationship, no exception is
thrown.
--
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
12:49 p.m.
New subject: [Hibernate-JIRA] Resolved: (HHH-5028) Calling em.remove() on child object @OneToMany relationship when CascadeType.ALL and FetchType.EAGER are set throws exception
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5028?page=c...
]
Gail Badner resolved HHH-5028.
------------------------------
Assignee: Gail Badner
Resolution: Rejected
Jesper, thanks for the analysis.
Calling em.remove() on child object @OneToMany relationship when
CascadeType.ALL and FetchType.EAGER are set throws exception
-----------------------------------------------------------------------------------------------------------------------------
Key: HHH-5028
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5028
Project: Hibernate Core
Issue Type: Bug
Components: entity-manager
Affects Versions: 3.5.0-CR-2, 3.5.1
Environment: Confirmed bug using MySQL, PostgreSQL, and Hsqldb, which is what the
test is configured with. Hibernate version is 3.5.0-CR-2 (see test app pom.xml)
Reporter: Jesse Hutton
Assignee: Gail Badner
Attachments: HibernateManyToOneEagerRemove.tar.gz
Calling em.remove(foo) on the child object of a @OneToMany relationship that is defined
with CascadeType.ALL and FetchType.EAGER throws an Exception. The cause is given as:
javax.persistence.EntityNotFoundException: deleted entity passed to persist:
And all I'm doing in the test is removing an object. See attached test case.
If, however, I remove FetchType.EAGER from the @OneToMany relationship, no exception is
thrown.
--
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:08 p.m.
New subject: [Hibernate-JIRA] Commented: (HHH-5028) Calling em.remove() on child object @OneToMany relationship when CascadeType.ALL and FetchType.EAGER are set throws exception
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5028?page=c...
]
Jesse Hutton commented on HHH-5028:
-----------------------------------
Jesper Steen Møller: I was expecting that the child object would be removed from the
database without a rather opaque exception being thrown.
I also wasn't expecting that calling em.remove(child) would have any side affects on
parents in the current persistence context. I don't know what's going on
underneath, but I assume that some state change in the parent had to be committed after
doing nothing but call em.remove(child) which caused the cascade to happen (the PERSIST
cascade?). IIRC, this doesn't happen when CASCADE is not set.
As there is no join table in OneToMany, it makes no sense to force client code to call
parent.getFooChildren().remove(foo) and then em.remove(foo). IIRC, I tested this in
eclipse link as well, and it didn't throw an exception.
Calling em.remove() on child object @OneToMany relationship when
CascadeType.ALL and FetchType.EAGER are set throws exception
-----------------------------------------------------------------------------------------------------------------------------
Key: HHH-5028
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5028
Project: Hibernate Core
Issue Type: Bug
Components: entity-manager
Affects Versions: 3.5.0-CR-2, 3.5.1
Environment: Confirmed bug using MySQL, PostgreSQL, and Hsqldb, which is what the
test is configured with. Hibernate version is 3.5.0-CR-2 (see test app pom.xml)
Reporter: Jesse Hutton
Assignee: Gail Badner
Attachments: HibernateManyToOneEagerRemove.tar.gz
Calling em.remove(foo) on the child object of a @OneToMany relationship that is defined
with CascadeType.ALL and FetchType.EAGER throws an Exception. The cause is given as:
javax.persistence.EntityNotFoundException: deleted entity passed to persist:
And all I'm doing in the test is removing an object. See attached test case.
If, however, I remove FetchType.EAGER from the @OneToMany relationship, no exception is
thrown.
--
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:10 p.m.
New subject: [Hibernate-JIRA] Issue Comment Edited: (HHH-5028) Calling em.remove() on child object @OneToMany relationship when CascadeType.ALL and FetchType.EAGER are set throws exception
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5028?page=c...
]
Jesse Hutton edited comment on HHH-5028 at 1/11/11 2:09 PM:
------------------------------------------------------------
Jesper Steen Møller: I was expecting that the child object would be removed from the
database without a rather opaque exception being thrown.
I also wasn't expecting that calling em.remove(child) would have any side affects on
parents in the current persistence context. I don't know what's going on
underneath, but I assume that some state change in the parent had to be committed after
doing nothing but call em.remove(child) which caused the cascade to happen (the PERSIST
cascade?). IIRC, this doesn't happen when CASCADE is not set.
As there is no join table in OneToMany, it makes no sense to force client code to call
parent.getFooChildren().remove(foo) and then em.remove(foo). IIRC, I tested this in
eclipse link as well, and it didn't throw an exception.
Edit: I also doubt that such a requirement (explicit removal from OneToMany collection
before child removal) is documented anywhere in the hibernate documentation, where as it
certainly is extensively with ManyToMany.
was (Author: jhutton):
Jesper Steen Møller: I was expecting that the child object would be removed from the
database without a rather opaque exception being thrown.
I also wasn't expecting that calling em.remove(child) would have any side affects on
parents in the current persistence context. I don't know what's going on
underneath, but I assume that some state change in the parent had to be committed after
doing nothing but call em.remove(child) which caused the cascade to happen (the PERSIST
cascade?). IIRC, this doesn't happen when CASCADE is not set.
As there is no join table in OneToMany, it makes no sense to force client code to call
parent.getFooChildren().remove(foo) and then em.remove(foo). IIRC, I tested this in
eclipse link as well, and it didn't throw an exception.
Calling em.remove() on child object @OneToMany relationship when
CascadeType.ALL and FetchType.EAGER are set throws exception
-----------------------------------------------------------------------------------------------------------------------------
Key: HHH-5028
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5028
Project: Hibernate Core
Issue Type: Bug
Components: entity-manager
Affects Versions: 3.5.0-CR-2, 3.5.1
Environment: Confirmed bug using MySQL, PostgreSQL, and Hsqldb, which is what the
test is configured with. Hibernate version is 3.5.0-CR-2 (see test app pom.xml)
Reporter: Jesse Hutton
Assignee: Gail Badner
Attachments: HibernateManyToOneEagerRemove.tar.gz
Calling em.remove(foo) on the child object of a @OneToMany relationship that is defined
with CascadeType.ALL and FetchType.EAGER throws an Exception. The cause is given as:
javax.persistence.EntityNotFoundException: deleted entity passed to persist:
And all I'm doing in the test is removing an object. See attached test case.
If, however, I remove FetchType.EAGER from the @OneToMany relationship, no exception is
thrown.
--
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
4927
days inactive
5222
days old
hibernate-issues@lists.jboss.org
7 comments
3 participants
participants (3)
-
Gail Badner (JIRA) -
Jesper Steen Møller (JIRA)
-
Jesse Hutton (JIRA)