예제 도메인 모델의 엔티티 클래스와 ERD를 보자.
db에서 FK가 다에 들어가야 하기 때문에 member에 들어간것을 확인할 수 있다.

Member class를 아래와 같이 설정을 해주고
package study.datajpa.entity;
import lombok.Getter;
import lombok.Setter;
import javax.persistence.*;
@Entity
@Getter @Setter
public class Member {
@Id
@GeneratedValue
@Column(name = "member_id")
private Long id;
private String username;
private int age;
// member와 team은 다대일 관계
@ManyToOne
@JoinColumn(name = "tema_id")
private Team team;
protected Member() {
}
public Member(String username) {
this.username = username;
}
}
Team을 아래와 같이 설정해준다.
package study.datajpa.entity;
import javax.persistence.Column;
import javax.persistence.Entity;
import javax.persistence.GeneratedValue;
import javax.persistence.Id;
@Entity
public class Team {
@Id
@GeneratedValue
@Column(name = "team_id")
private Long id;
private String name;
}
Team Class
package study.datajpa.entity;
import javax.persistence.Column;
import javax.persistence.Entity;
import javax.persistence.GeneratedValue;
import javax.persistence.Id;
import java.util.ArrayList;
import java.util.List;
@Entity
public class Team {
@Id
@GeneratedValue
@Column(name = "team_id")
private Long id;
private String name;
private List<Member> members = new ArrayList<>();
}
mappedBy는 FK가 없는쪽에다가 걸어준다.(Team class)
package study.datajpa.entity;
import javax.persistence.*;
import java.util.ArrayList;
import java.util.List;
@Entity
public class Team {
@Id
@GeneratedValue
@Column(name = "team_id")
private Long id;
private String name;
@OneToMany(mappedBy = "team")
private List<Member> members = new ArrayList<>();
}
그리고 Member Class에 있는 protected Member를 지우고 NoArgsConstructor를 설정해준다.
ToString도 넣어준다.
package study.datajpa.entity;
import lombok.*;
import javax.persistence.*;
@Entity
@Getter
@Setter
@NoArgsConstructor(access = AccessLevel.PROTECTED)
@ToString(of = {"id", "username", "age"})
public class Member {
@Id
@GeneratedValue
@Column(name = "member_id")
private Long id;
private String username;
private int age;
@ManyToOne
@JoinColumn(name = "tema_id")
private Team team;
public Member(String username) {
this.username = username;
}
}
Team Class도 아래와 같이 설정해준다.
// Team Class
package study.datajpa.entity;
import lombok.*;
import javax.persistence.*;
import java.util.ArrayList;
import java.util.List;
@Entity
@Getter @Setter
@NoArgsConstructor(access = AccessLevel.PROTECTED)
@ToString(of = {"id", "name"})
public class Team {
@Id
@GeneratedValue
@Column(name = "team_id")
private Long id;
private String name;
@OneToMany(mappedBy = "team")
private List<Member> members = new ArrayList<>();
public Team(Long id, String name, List<Member> members) {
this.name = name;
}
}
그리고 서로 연관관계를 mapping하는 세팅을 해줘야 한다.
// Member Class
package study.datajpa.entity;
import lombok.*;
import javax.persistence.*;
@Entity
@Getter
@Setter
@NoArgsConstructor(access = AccessLevel.PROTECTED)
@ToString(of = {"id", "username", "age"})
public class Member {
@Id
@GeneratedValue
@Column(name = "member_id")
private Long id;
private String username;
private int age;
@ManyToOne
@JoinColumn(name = "tema_id")
private Team team;
public Member(String username) {
this.username = username;
}
// 이 부분 코드를 추가해서 세팅
public void changeTeam(Team team) {
this.team = team;
team.getMembers().add(this);
}
}
MemberTest도 설정을 해준다.
설정을 해줄 때
MemberTest에서 Member member1 = new Member("member1", 10, teamA); 이 부분을 해줄 때
member class 에서 Create Constructor을 설정해준다.
// MemberTest
package study.datajpa.entity;
import org.junit.jupiter.api.Test;
import org.springframework.boot.test.context.SpringBootTest;
import org.springframework.test.annotation.Rollback;
import org.springframework.transaction.annotation.Transactional;
import javax.persistence.EntityManager;
import javax.persistence.PersistenceContext;
import static org.junit.jupiter.api.Assertions.*;
@SpringBootTest
@Transactional
@Rollback(false)
class MemberTest {
@PersistenceContext
EntityManager em;
@Test
public void testEntity() {
Team teamA = new Team("teamA");
Team teamB = new Team("teamB");
em.persist(teamA);
em.persist(teamB);
// 이 부분 세팅 해줄 때
Member member1 = new Member("member1", 10, teamA);
}
}
member class를 아래와 같이 해준다.
package study.datajpa.entity;
import lombok.*;
import javax.persistence.*;
@Entity
@Getter
@Setter
@NoArgsConstructor(access = AccessLevel.PROTECTED)
@ToString(of = {"id", "username", "age"})
public class Member {
@Id
@GeneratedValue
@Column(name = "member_id")
private Long id;
private String username;
private int age;
@ManyToOne
@JoinColumn(name = "tema_id")
private Team team;
public Member(String username) {
this.username = username;
}
// 이 부분 세팅
public Member(String username, int age, Team team) {
this.username = username;
this.age = age;
if (team != null) {
changeTeam(team);
}
}
public void changeTeam(Team team) {
this.team = team;
team.getMembers().add(this);
}
}
MemberTest에서 flush를 해주는데 db에 INSERT쿼리를 강제로 다 날려준다.(persist해서 영속성 컨텍스트에서 member랑 team을 다 모아놓은 상태에서)
그리고 em.clear을 해주게 되는데 db에 쿼리를 다 날린 상태에서 JPA의 영속성 컨텍스트에 있는 캐시를 다 날려버린다.
// MemberTest
package study.datajpa.entity;
import org.junit.jupiter.api.Test;
import org.springframework.boot.test.context.SpringBootTest;
import org.springframework.test.annotation.Rollback;
import org.springframework.transaction.annotation.Transactional;
import javax.persistence.EntityManager;
import javax.persistence.PersistenceContext;
import static org.junit.jupiter.api.Assertions.*;
@SpringBootTest
@Transactional
@Rollback(false)
class MemberTest {
@PersistenceContext
EntityManager em;
@Test
public void testEntity() {
Team teamA = new Team("teamA");
Team teamB = new Team("teamB");
em.persist(teamA);
em.persist(teamB);
Member member1 = new Member("member1", 10, teamA);
Member member2 = new Member("member2", 10, teamA);
Member member3 = new Member("member3", 10, teamB);
Member member4 = new Member("member4", 10, teamB);
em.persist(member1);
em.persist(member2);
em.persist(member3);
em.persist(member4);
em.flush();
em.clear();
}
}
MemberTest에서 JPQL을 이제 짜고 확인을 해보면 빌드로그가 아래와 같다.
// 순수 JPA로 생성
package study.datajpa.entity;
import org.junit.jupiter.api.Test;
import org.springframework.boot.test.context.SpringBootTest;
import org.springframework.test.annotation.Rollback;
import org.springframework.transaction.annotation.Transactional;
import javax.persistence.EntityManager;
import javax.persistence.PersistenceContext;
import java.util.List;
import static org.junit.jupiter.api.Assertions.*;
@SpringBootTest
@Transactional
@Rollback(false)
class MemberTest {
@PersistenceContext
EntityManager em;
@Test
public void testEntity() {
Team teamA = new Team("teamA");
Team teamB = new Team("teamB");
em.persist(teamA);
em.persist(teamB);
Member member1 = new Member("member1", 10, teamA);
Member member2 = new Member("member2", 20, teamA);
Member member3 = new Member("member3", 30, teamB);
Member member4 = new Member("member4", 40, teamB);
em.persist(member1);
em.persist(member2);
em.persist(member3);
em.persist(member4);
// 초기화
em.flush();
em.clear();
// 확인 =
List<Member> members = em.createQuery("select m from Member m", Member.class)
.getResultList();
for (Member member : members) {
System.out.println("member = " + member);
System.out.println("-> member.team = " + member.getTeam());
}
}
}
2022-04-15 18:39:10.190 TRACE 12189 --- [ main] org.hibernate.type.CollectionType : Created collection wrapper: [study.datajpa.entity.Team.members#2]
member = Member(id=3, username=member1, age=10)
-> member.team = Team(id=1, name=teamA)
member = Member(id=4, username=member2, age=20)
-> member.team = Team(id=1, name=teamA)
member = Member(id=5, username=member3, age=30)
-> member.team = Team(id=2, name=teamB)
member = Member(id=6, username=member4, age=40)
-> member.team = Team(id=2, name=teamB)
2022-04-15 18:39:10.258 INFO 12189 --- [ main] p6spy : #1650015550258 | took 1ms | commit | connection 3| url jdbc:h2:tcp://localhost/~/datajpa
h2 DB에서도 확인을 해보면 member와 team이 연관관계 세팅이 된것을 확인할 수 있다.

그리고 member에서 ManyToOne의 기본값이 EAGER로 되어있는데 이걸 LAZY로 바꿔준다.(모든 연관관계는 지연로딩 LAZY로 세팅을 해줘야 한다.)
package study.datajpa.entity;
import lombok.*;
import javax.persistence.*;
import static javax.persistence.FetchType.*;
@Entity
@Getter
@Setter
@NoArgsConstructor(access = AccessLevel.PROTECTED)
@ToString(of = {"id", "username", "age"})
public class Member {
@Id
@GeneratedValue
@Column(name = "member_id")
private Long id;
private String username;
private int age;
// ManyToOne은 기본값이 EAGER이므로 LAZY로 바꿔준다.
@ManyToOne(fetch = LAZY)
@JoinColumn(name = "tema_id")
private Team team;
public Member(String username) {
this.username = username;
}
public Member(String username, int age, Team team) {
this.username = username;
this.age = age;
if (team != null) {
changeTeam(team);
}
}
public void changeTeam(Team team) {
this.team = team;
team.getMembers().add(this);
}
}
빌드를 해보면 팀 조회하는 쿼리들이 나가고
select team0_.team_id as team_id1_1_0_, team0_.name as name2_1_0_ from team team0_ where team0_.team_id=?
select team0_.team_id as team_id1_1_0_, team0_.name as name2_1_0_ from team team0_ where team0_.team_id=1;
아래와 같이 나가게 된다.
-> member.team = Team(id=1, name=teamA)
member = Member(id=4, username=member2, age=20)
-> member.team = Team(id=1, name=teamA)
member = Member(id=5, username=member3, age=30)
이제 예제 도메인 모델을 가지고 스프링 데이터 JPA 기능들을 하나씩 알아보자.

<출처 김영한: 실전! 스프링 데이터 JPA >
실전! 스프링 데이터 JPA - 인프런 | 강의
스프링 데이터 JPA는 기존의 한계를 넘어 마치 마법처럼 리포지토리에 구현 클래스 없이 인터페이스만으로 개발을 완료할 수 있습니다. 그리고 반복 개발해온 기본 CRUD 기능도 모두 제공합니다.
www.inflearn.com
'Spring > SpringDataJPA' 카테고리의 다른 글
메소드 이름으로 쿼리 생성 (0) | 2022.04.15 |
---|---|
공통 인터페이스 분석 (0) | 2022.04.15 |
공통 인터페이스 설정 & 적용 (0) | 2022.04.15 |
공통 인터페이스 기반 - 순수 JPA 기반 레포지토리 만들기 (0) | 2022.04.15 |
프로젝트 생성 & 스프링 데이터 JPA와 DB설정, 동작확인 (0) | 2022.04.15 |