Spring JPA中一对多关联对象无法删除问题求助

我正在开发一个包含发布帖子、评论和点赞功能的项目，目前遇到的问题是：尝试删除Post、Comment或Like对象时，JPA并未从数据库中删除对应的记录。我已在一对多关联中添加了orphanRemoval = true，但问题仍未解决。

相关代码 #

User实体类 #

@Entity
@Getter @Setter @ToString
public class User {

    @Id
    @GeneratedValue(strategy= GenerationType.AUTO,generator="native")
    @GenericGenerator(name = "native",strategy = "native")
    private Long userId;

    @Pattern(regexp = CommunicationConstants.EMAIL_REGEX_PATTERN, message = CommunicationConstants.PATTERN_DOES_NOT_MATCH_MESSAGE)
    private String email;

    @JsonProperty(access = JsonProperty.Access.WRITE_ONLY)
    @Pattern(regexp = SecurityConstants.PASSWORD_REGEX, message = "INVALID PASSWORD")
    private String password;

    @JsonIgnore
    @OneToMany (mappedBy = "user", fetch = FetchType.EAGER, cascade = CascadeType.ALL)
    private Set<Authority> authorities;

    @OneToMany (mappedBy = "user", fetch = FetchType.EAGER, cascade = CascadeType.ALL, orphanRemoval = true)
    private List<Comment> comments;

    @OneToMany (mappedBy = "user", fetch = FetchType.EAGER, cascade = CascadeType.ALL, orphanRemoval = true)
    private List<Post> posts;

    @OneToMany (mappedBy = "user", fetch = FetchType.EAGER, cascade = CascadeType.ALL, orphanRemoval = true)
    private List<Likes> likes;
}

Post实体类 #

@Entity
@Getter @Setter
public class Post {

    @Id
    @GeneratedValue(strategy= GenerationType.AUTO,generator="native")
    @GenericGenerator(name = "native",strategy = "native")
    private Long postId;

    @OneToMany (mappedBy = "post", fetch = FetchType.EAGER, cascade = CascadeType.ALL, orphanRemoval = true)
    private List<Comment> comments;

    @OneToMany (mappedBy = "post", fetch = FetchType.EAGER, cascade = CascadeType.ALL, orphanRemoval = true)
    private List<Likes> likes;

    @ManyToOne(fetch = FetchType.LAZY)
    @OnDelete(action = OnDeleteAction.CASCADE)
    @JsonIgnore
    @JoinColumn (name = "user_id")
    private User user;
}

Comment和Like实体类结构与Post类似。

PostService类 #

@Service
@AllArgsConstructor
public class PostService {

    private final PostRepository postRepository;

    public Result createNewPost (Post post) {

        try {
            post.setComments(new ArrayList<>());
            post.setCreatedAt(new Date());
            return new DataResult<>(true, NEW_POST_CREATED, postRepository.save(post));
        }
        catch (Exception e) {
            return new Result(false, e.getMessage());
        }
    }

    public Result deletePost(Post post, User user) {

        if (post == null) {
            return new Result(false, POST_NOT_FOUND);
        }
        else if (post.getUser().equals(user)) {
            try {
                postRepository.delete(post);
                return new Result(true, POST_DELETED);
            }
            catch (Exception e) {
                e.printStackTrace();
                return new Result(false, e.getMessage());
            }
        }
        else {
            return new Result(false, PERMISSION_DENIED);
        }
    }
}

调用deletePost()方法时，既没有删除数据库记录，也没有抛出异常。

问题排查与解决方案 #

1. 传入的Post对象非持久化实例 #

JPA的delete()方法仅对当前持久化上下文管理的对象生效（即从数据库查询得到的实例）。如果传入的是新建对象、或者脱离了持久化上下文的对象（比如DTO转换而来），JPA不会执行删除操作，也不会抛出异常。

修复方案：
修改deletePost方法，先通过ID查询持久化实例再删除，或直接使用deleteById()：

@Transactional
public Result deletePost(Long postId, User user) {
    Optional<Post> postOpt = postRepository.findById(postId);
    if (postOpt.isEmpty()) {
        return new Result(false, POST_NOT_FOUND);
    }
    Post post = postOpt.get();
    if (!post.getUser().equals(user)) {
        return new Result(false, PERMISSION_DENIED);
    }
    try {
        postRepository.deleteById(postId);
        return new Result(true, POST_DELETED);
    } catch (Exception e) {
        e.printStackTrace();
        return new Result(false, e.getMessage());
    }
}

2. 事务未正确提交 #

如果deletePost方法没有被事务管理，JPA的操作不会同步到数据库。检查方法是否添加了@Transactional注解，或Spring事务配置是否正确。

修复方案：
在deletePost方法上添加@Transactional注解，确保操作在事务中执行并提交。

3. 关联关系维护逻辑问题 #

orphanRemoval = true仅在从父集合中移除子对象时生效（比如从user.getPosts()中移除某个Post），而非直接调用子对象的delete()方法时生效。直接删除子对象需确保父对象的关联引用被正确处理，或依赖数据库级别的外键级联删除。

另外，@OnDelete(action = OnDeleteAction.CASCADE)是Hibernate扩展，会生成数据库级联删除约束，但需确认数据库中外键约束已正确创建。

4. FetchType.EAGER的潜在问题 #

大量使用FetchType.EAGER会导致删除时加载过多关联数据，可能引发持久化上下文状态不一致。建议将非必要的关联改为FetchType.LAZY，优化性能并避免状态冲突。

内容的提问来源于stack exchange，提问作者Adem Galitekin