#2143 new
Deleted User

Hibernate delete silently failing

Reported by Deleted User | January 15th, 2018 @ 07:35 PM

I have a web application with three models: Classroom, Student and Group (see details). Each model has exactly one instance in database, and those instances are related to each other. Ideally, deleting a classroom should also delete it's groups, and dissociate it's students, deleting a student should dissociate it's classrooms and groups, and deleting a group should dissociate it's students, but it is not working.

When I try to delete a classroom, a student or a group they are simply not deleted. No runtime exception, no SQL error, no nothing. It just fails silently. I set jpa.debugSQL=true and don't see any delete statement issued, just selects.

Somehow, courses with groups not related to students are deleted correctly.

Framework version: 1.5.0
Platform you're using: Linux (Ubuntu 16.04, openjdk-8)

Reproduction steps:

  1. Try to .delete() a Classroom, Group or Student object
  2. Should delete object and cascade deletion to children objects, but does not delete anything


Source code with unit test cases is available on GitHub

   [One]                        [Many]
     |                           /
     |                          /
   [Many]                      /
@Entity(name = "r_classroom")
public class Classroom extends Model {
    @OneToMany(mappedBy = "classroom", cascade = CascadeType.ALL, orphanRemoval = true)
    public List<Group> groups = new ArrayList<>();

    @ManyToMany(mappedBy = "classrooms", cascade = {CascadeType.PERSIST, CascadeType.MERGE})
    public List<Student> students = new ArrayList<>();

    public String name;

@Entity(name = "r_student")
public class Student extends Model {
    @ManyToMany(cascade = {CascadeType.PERSIST, CascadeType.MERGE})
    public List<Classroom> classrooms = new ArrayList<>();

    @ManyToMany(cascade = {CascadeType.MERGE, CascadeType.PERSIST})
    public List<Group> groups = new ArrayList<>();

    public String name;

@Entity(name = "r_group")
public class Group extends Model {
    public Classroom classroom;

    @ManyToMany(mappedBy = "groups", cascade = {CascadeType.PERSIST, CascadeType.MERGE})
    public List<Student> students = new ArrayList<>();

    public String name;

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.