#1847 confirmed
Thomas Parle

Orphan removal not cascaded for @OneToOne relationships

Reported by Thomas Parle | July 7th, 2014 @ 10:34 PM | in 1.4.x

Framework version: 1.3 RC 1
Platform you're using: Linux Ubuntu 14.04

Reproduction steps:
- use the project attached as a zip file - run the test (there is only one) to reproduce the error

the bug seems to be related to a @OneToOne association whose entity is to be deleted by setting its reference to 'null'. As 'orphanRemoval' is set to true, the entity should be deleted, but the foreign keys related to this entity ('Animal' in the sample project) do not trigger the proper delete on tables that references this entity (here, the table 'Animal_Meal').
In Play 1.2.x, I used a hack to manually remove these dependencies with a @PreRemove callback, but in Play 1.3 it causes a StackOverflowException.

It seems that this bug is related to Hibernate, and seems to have been fixed in versions 4.2.7 and 4.3.0, see:
- https://hibernate.atlassian.net/browse/HHH-6484 - http://stackoverflow.com/questions/20280271/hibernate-jpa-onetoone-...

Maybe a simple upgrade of Hibernate would fix this issue (the version used by Play 1.3RC1 is 4.1.3)
Hope it helps !

Comments and changes to this ticket

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »

<h2>Play framework</h2>

Play makes it easier to build Web applications with Java. It is a clean alternative to bloated Enterprise Java stacks. It focuses on developer productivity and targets RESTful architectures. Learn more on the <a href="http://www.playframework.org">http://www.playframework.org</a> website.<br><br>

<h2>Source code is hosted on github</h2>Check out our repository at <a href="http://github.com/playframework/play">http://github.com/playframework/play</a><br><br>

<h2>Contributing, creating a patch</h2> Please read the <a href="http://play.lighthouseapp.com/projects/57987/contributor-guide">contributor guide</a><br><br>

<h2>Reporting Security Vulnerabilities</h2> Since all bug reports are public, please report any security vulnerability directly to <em>guillaume dot bort at gmail dot com</em>.<br><br>

<h2>Creating a bug report</h2> Bug reports are incredibly helpful, so take time to report bugs and request features in our ticket tracker. We’re always grateful for patches to Play’s code. Indeed, bug reports with attached patches will get fixed far quickly than those without any.<br><br>

Please include as much relevant information as possible including the exact framework version you're using and a code snippet that reproduces the problem.<br><br>

Don't have too much expectations. Unless the bug is really a serious "everything is broken" thing, you're creating a ticket to start a discussion. Having a patch (or a branch on Github we can pull from) is better, but then again we'll only pull high quality branches that make sense to be in the core of Play.


Referenced by