从多对一关联侧持久化实体时事务回滚问题求助

一、背景信息 #

数据库关联与期望效果 #

数据库包含student、student_subscription、library_subscription/course_subscription三张表，采用Joined Table继承实现订阅类型区分，期望学生可关联对应类型的订阅记录。

JPA实体建模 #

Student实体

@Entity 
@Table(name = "student")
public class Student {
    @Id
    @SequenceGenerator(name = "student_pk_generator", sequenceName = 
                              "student_pk_sequence", allocationSize = 1)
    @GeneratedValue(strategy = GenerationType.SEQUENCE, generator = 
                               "student_pk_generator")
    @Column(name = "student_id", nullable = false)
    private Long studentId;

    @Column(name = "name", nullable = false)
    private String studentName;

    @OneToMany(mappedBy = "student", cascade = CascadeType.ALL)
    private Set<StudentSubscription> studentSubscription;
}

StudentSubscription抽象实体

@Entity
@Table(name = "student_subscription")
@Inheritance(strategy = InheritanceType.JOINED)
public abstract class StudentSubscription {
    @Id
    private Long studentId;

    @ManyToOne(optional = false)
    @JoinColumn(name = "student_id", referencedColumnName = "student_id")
    @MapsId
    private Student student;

    @Column(name = "valid_from")
    private Date validFrom;

    @Column(name = "valid_to")
    private Date validTo;
}

LibrarySubscription实体

@Entity
@Table(name = "library_subscription", 
       uniqueConstraints = {@UniqueConstraint(columnNames = {"library_code"})})
@PrimaryKeyJoinColumn(name = "student_id")
public class LibrarySubscription extends StudentSubscription {

    @Column(name = "library_code", nullable = false)
    private String libraryCode;

    @PrePersist
    private void generateLibraryCode() {
        this.libraryCode = // 生成唯一libraryCode的逻辑
    }
}

CourseSubscription实体

@Entity
@Table(name = "course_subscription", 
       uniqueConstraints = {@UniqueConstraint(columnNames = {"course_code"})})
@PrimaryKeyJoinColumn(name = "student_id")
public class CourseSubscription extends StudentSubscription {

    @Column(name = "course_code", nullable = false)
    private String courseCode;

    @PrePersist
    private void generateCourseCode() {
        this.courseCode = // 生成唯一courseCode的逻辑
    }
}

二、测试场景与异常 #

现有id为100的已持久化Student，测试代码如下：

@Test
public void testLibrarySubscriptionPersist() {
    Student student = studentRepository.findById(100L).get();
    StudentSubscription librarySubscription = new LibrarySubscription();
    librarySubscription.setValidFrom(// 某日期);
    librarySubscription.setValidTo(// 某日期);
    librarySubscription.setStudent(student);
    studentSubscriptionRepository.save(librarySubscription);
}

异常1：游离实体异常 #

运行测试抛出：

org.springframework.dao.InvalidDataAccessApiUsageException: detached entity passed to persist: com.springboot.data.jpa.entity.Student; nested exception is org.hibernate.PersistentObjectException: detached entity passed to persist: com.springboot.data.jpa.entity.Student

异常2：事务回滚无数据持久化 #

给测试方法添加@Transactional后，游离异常消失，但数据未持久化，日志显示事务被回滚：

INFO 3515 --- [           main] o.s.t.c.transaction.TransactionContext   : Rolled back transaction for test: [DefaultTestContext@35390ee3 testClass = SpringDataJpaApplicationTests, testInstance = com.springboot.data.jpa.SpringDataJpaApplicationTests@48a12036, testMethod = testLibrarySubscriptionPersist@SpringDataJpaApplicationTests, testException = [null], mergedContextConfiguration = [MergedContextConfiguration@5e01a982 testClass = SpringDataJpaApplicationTests, locations = '{}', classes = '{class com.springboot.data.jpa.SpringDataJpaApplication}', contextInitializerClasses = '[]', activeProfiles = '{}', propertySourceLocations = '{}', propertySourceProperties = '{org.springframework.boot.test.context.SpringBootTestContextBootstrapper=true}', contextCustomizers = set[org.springframework.boot.test.context.filter.ExcludeFilterContextCustomizer@18ece7f4, org.springframework.boot.test.json.DuplicateJsonObjectContextCustomizerFactory$DuplicateJsonObjectContextCustomizer@264f218, org.springframework.boot.test.mock.mockito.MockitoContextCustomizer@0, org.springframework.boot.test.web.client.TestRestTemplateContextCustomizer@2462cb01, org.springframework.boot.test.autoconfigure.actuate.metrics.MetricsExportContextCustomizerFactory$DisableMetricExportContextCustomizer@928763c, org.springframework.boot.test.autoconfigure.properties.PropertyMappingContextCustomizer@0, org.springframework.boot.test.autoconfigure.web.servlet.WebDriverContextCustomizerFactory$Customizer@7c3fdb62, org.springframework.boot.test.context.SpringBootTestArgs@1, org.springframework.boot.test.context.SpringBootTestWebEnvironment@1ad282e0], contextLoader = 'org.springframework.boot.test.context.SpringBootContextLoader', parent = [null]], attributes = map['org.springframework.test.context.event.ApplicationEventsTestExecutionListener.recordApplicationEvents' -> false]]

三、疑问与解答 #

疑问1：为何出现游离实体异常？ #

原因：
无事务的测试方法中，studentRepository.findById(100L)执行完成后，EntityManager会立即关闭，查询返回的Student实体脱离持久化上下文，成为游离态（detached）。当调用studentSubscriptionRepository.save()时，Hibernate需要处理关联的Student实体，但该实体已不在持久化上下文中，且StudentSubscription的@ManyToOne未配置cascade = CascadeType.MERGE，无法自动合并游离实体，因此抛出异常。

疑问2：添加@Transactional后为何事务回滚、数据未持久化？ #

原因：
Spring Test框架中，标注@Transactional的测试方法默认会在测试结束后自动回滚事务，这是框架的默认行为，用于避免测试数据污染数据库环境。因此即使代码执行了save操作，事务最终会被回滚，数据不会写入数据库。

四、解决方案 #

针对游离实体异常的解决方法 #

1. 给测试方法添加@Transactional：让EntityManager在整个测试方法周期内保持打开，Student实体始终处于持久化上下文，不会变成游离态。
2. 配置级联合并：在StudentSubscription的@ManyToOne注解中添加cascade = CascadeType.MERGE，让Hibernate在保存订阅时自动合并游离的Student实体：

   @ManyToOne(optional = false, cascade = CascadeType.MERGE)
   @JoinColumn(name = "student_id", referencedColumnName = "student_id")
   @MapsId
   private Student student;
   

3. 手动合并游离实体：在保存订阅前，先将Student重新附加到持久化上下文：

   Student student = studentRepository.findById(100L).get();
   student = studentRepository.save(student); // 执行merge操作，将游离实体重新关联到上下文
   

针对事务回滚的解决方法 #

如果希望测试数据持久化到数据库，可通过以下方式修改测试方法：

• 添加@Rollback(false)注解，禁用默认回滚：

  @Test
  @Transactional
  @Rollback(false)
  public void testLibrarySubscriptionPersist() {
      // ... 测试代码
  }
  

• 或者添加@Commit注解，显式提交事务：

  @Test
  @Transactional
  @Commit
  public void testLibrarySubscriptionPersist() {
      // ... 测试代码
  }
  

五、额外注意事项 #

• 当前实体建模中，StudentSubscription以student_id作为主键，意味着每个学生只能拥有一个同类型的订阅（比如一个学生只能有一条LibrarySubscription记录）。如果业务需求允许一个学生拥有多条同类型订阅，需要调整主键设计（例如添加自增ID或额外的唯一标识字段）。
• 需确保@PrePersist中的libraryCode/courseCode生成逻辑能生成唯一值，否则会触发数据库唯一约束违反，导致事务回滚。

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