如何通过Spring JPA关联表创建嵌套对象？解决加载异常问题

尝试通过Spring JPA关联多张表获取嵌套对象，但仓库查询存在问题，遇到LazyInitializationException，设置FetchType.EAGER还会触发StackOverflow错误。

期望输出（简化示例） #

[departmentId: 1
 departmentName: A
 employees:[
    [employeeId: 100
    employeeName: John],
    [employeeId: 200
    employeeName: Carl]],
[departmentId: 2
 departmentName: B
 employees:[
    [employeeId: 300
    employeeName: Nancy]]

PostgreSQL表结构 #

• department表：department_id, department_name
• employees表：employee_id, employee_name, department_id

实体类代码 #

Department #

@Entity
@Table(name="department")
public class Department implements Serializable {

    @Id
    @Column(name="department_id")
    private Integer departmentId;

    @Column(name="department_name")
    private String departmentName;

    @OneToMany(mappedBy = "department")
    private List<Employee> employees;
    // getters, setters, etc.
}

Employee #

@Entity
@Table(name="employees")
public class Employee implements Serializable {

    @Id
    @Column(name="employee_id")
    private Integer employeeId;

    @Column(name="employee_name")
    private String employeeName;

    @ManyToOne
    @JoinColumn(name="department_id")
    private Department department;
    // getters, setters, etc.
}

Repository代码 #

@Repository
public interface Repository extends JpaRepository<Department, Integer> {

    @Query(value = "SELECT department.department_id, department_name, employee_id,  employee_name FROM department " +
            "JOIN employees ON employees.department_id = department.department_id", nativeQuery = true)
    List<Department> findDeps();
}

1. 修复原生查询的问题 #

你当前用的原生查询返回的是关联后的扁平结果集，Spring JPA无法自动将其映射为带嵌套employees的Department对象。原生查询适合简单数据场景，嵌套对象映射需要手动处理，不如改用JPQL或Spring Data JPA的派生查询更省心。

2. 用JPQL的JOIN FETCH解决懒加载异常 #

懒加载异常的核心原因是在事务外部访问了未初始化的employees集合。使用JOIN FETCH可以在一次查询中同时加载部门和关联的员工，既避免懒加载问题，也不会产生N+1查询的性能损耗：

@Repository
public interface DepartmentRepository extends JpaRepository<Department, Integer> {

    @Query("SELECT d FROM Department d JOIN FETCH d.employees")
    List<Department> findAllWithEmployees();
}

注：把接口名改为DepartmentRepository更规范，避免和Spring自带的Repository接口重名。

3. 解决StackOverflow错误的根源 #

设置FetchType.EAGER后出现栈溢出，是因为Department和Employee双向引用，序列化（比如返回给前端）时会无限递归。解决方法二选一：

• 在Employee的department字段上加@JsonIgnore，切断序列化时的递归链：

@ManyToOne
@JoinColumn(name="department_id")
@JsonIgnore
private Department department;

• 用@JsonManagedReference和@JsonBackReference标记双向关联：
  • 在Department的employees字段加@JsonManagedReference
  • 在Employee的department字段加@JsonBackReference

4. 规范写法建议 #

• 接口名避免使用Repository这类通用名称，改成DepartmentRepository符合Spring Data的命名规范
• 如果业务不需要双向关联，可以直接去掉Employee中的department字段，改用单向@OneToMany，降低代码复杂度
• 确保数据操作在事务内执行，比如在Service层方法上添加@Transactional注解（不过用JOIN FETCH的话，事务外也能正常访问集合）

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