I have 3 tables. `post`, `tag` and a join table `post_tag`. `post` to `post_tag` is one to many and `post_tag` to `tag` is one to one.
three entities are as follow:
Code:
@Entity
@Table(name = "post")
public class Post extends BaseEntity {
@Setter
@Getter
@OneToMany(cascade = CascadeType.ALL)
@JoinColumn(name = "post_id")
private Set<PostTag> tags;
}
@Entity
@Table(name = "post_tag")
public class PostTag extends BaseEntity {
@Setter
@Getter
@OneToOne(cascade = CascadeType.ALL, orphanRemoval = true)
private Tag tag;
}
@Entity
@Table(name = "tag")
public class Tag extends BaseEntity {
@Getter
@Setter
@Column(name = "tag_text")
private String text;
}
and My BaseEntity has just one variable
Code:
public class BaseEntity {
@Id
@Setter
@Getter
@Column(name = "id")
@GeneratedValue(strategy = GenerationType.IDENTITY)
Long id;
}
The above works great on update and insert, but it nulls the post_id in post_tag table when I wanted hibernate to delete the row instead.
What happened was for example client HAD 2 records in post_tag table. When doing a PUT request to update post, it also passes tags object with just 1 record. Hibernate is smart enough to keep the one in object and null the other, but what I really want hibernate to do is to delete the orphan record. I've tried to set orphanRemoval = true) like this to tags
Code:
@Setter
@Getter
@OneToMany(orphanRemoval = true)
@JoinColumn(name = "user_id")
private Set<UserSubscribeTag> tags;
but got
Code:
A collection with cascade=\"all-delete-orphan\" was no longer referenced by the owning entity instance
I don't know if this is possible since I think hibernate is doing the right thing. I should've called delete instead of save if I really want to get rid of that record.
Login
FAQ
Search
