Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DB 설계 #3

Closed
memoer opened this issue Jun 9, 2022 · 0 comments · Fixed by #26 or #28
Closed

DB 설계 #3

memoer opened this issue Jun 9, 2022 · 0 comments · Fixed by #26 or #28
Assignees
Labels
Type: Setting 개발 환경 설정

Comments

@memoer
Copy link
Contributor

memoer commented Jun 9, 2022

해당 이슈에 대한 설명을 적어주세요

AirJnC 프로젝트에 사용할 DB를 설계합니다.

해당 이슈가 왜 필요한가요?

프로젝트 진행시 DB를 사용하기로 결정하였고, 이를 위해선 DB Table이 필요합니다.
때문에, DB를 설계해야 합니다.

기타

그 외로 적어야 할 것들을 적어주세요

@memoer memoer added the chore label Jun 9, 2022
@memoer memoer self-assigned this Jun 9, 2022
@memoer memoer added this to To do in AirJnC Project via automation Jun 9, 2022
@memoer memoer mentioned this issue Jun 9, 2022
@memoer memoer removed chore labels Jun 10, 2022
@memoer memoer added the Type: Setting 개발 환경 설정 label Jun 10, 2022
@memoer memoer added this to the 초기 설정 milestone Jun 10, 2022
hoon25 pushed a commit that referenced this issue Jun 11, 2022
hoon25 added a commit that referenced this issue Jun 11, 2022
hoon25 added a commit that referenced this issue Jun 11, 2022
memoer added a commit that referenced this issue Jun 13, 2022
@memoer memoer mentioned this issue Jun 13, 2022
memoer added a commit that referenced this issue Jun 14, 2022
memoer added a commit that referenced this issue Jun 15, 2022
memoer added a commit that referenced this issue Jun 15, 2022
memoer added a commit that referenced this issue Jun 15, 2022
memoer added a commit that referenced this issue Jun 15, 2022
memoer added a commit that referenced this issue Jun 16, 2022
- 테이블 이름 변경
  - room_category -> room_root_category
  - room_category_detail -> room_leaf_category
  - room_category_detail__room_type -> room_category
- room_leaf_category에 컬럼 추가 `is_several_rooms`
  - 해당 카테고리를 선택한 방은 방의 개수를 설정해야 한다/안한다 여부
- room_price 테이블의 `weekly_price` 컬럼 이름 변경 -> `weekly_discount_price`
memoer added a commit that referenced this issue Jun 16, 2022
AirJnC Project automation moved this from To do to Done Jun 16, 2022
memoer added a commit that referenced this issue Jun 16, 2022
memoer added a commit that referenced this issue Jun 16, 2022
- 테이블 이름 변경
  - room_category -> room_root_category
  - room_category_detail -> room_leaf_category
  - room_category_detail__room_type -> room_category
- room_leaf_category에 컬럼 추가 `is_several_rooms`
  - 해당 카테고리를 선택한 방은 방의 개수를 설정해야 한다/안한다 여부
- room_price 테이블의 `weekly_price` 컬럼 이름 변경 -> `weekly_discount_price`
memoer added a commit that referenced this issue Jun 16, 2022
memoer added a commit that referenced this issue Jun 17, 2022
memoer added a commit that referenced this issue Jun 17, 2022
memoer added a commit that referenced this issue Jun 17, 2022
memoer added a commit that referenced this issue Jun 17, 2022
memoer added a commit that referenced this issue Jun 17, 2022
memoer added a commit that referenced this issue Jun 17, 2022
memoer added a commit that referenced this issue Jun 17, 2022
memoer added a commit that referenced this issue Jun 17, 2022
memoer added a commit that referenced this issue Jun 17, 2022
- category 관련 테이블 모두 room_category 테이블로 묶음
- facility_category 테이블은 facilitry 테이블의 category 컬럼으로 넣음
- 고정 데이터들은 자바 애플리케이션 단에서 ENUM으로 관리하기로 결정
memoer added a commit that referenced this issue Jun 21, 2022
- category name 하나만 가져가기로 결정
- 해당 컬럼의 값 -> "부티크 호텔, 게스트 하우스, 저택, 아파트, ... "
memoer added a commit that referenced this issue Jun 21, 2022
- category 관련 테이블 모두 room_category 테이블로 묶음
- facility_category 테이블은 facilitry 테이블의 category 컬럼으로 넣음
- 고정 데이터들은 자바 애플리케이션 단에서 ENUM으로 관리하기로 결정
memoer added a commit that referenced this issue Jun 21, 2022
- category name 하나만 가져가기로 결정
- 해당 컬럼의 값 -> "부티크 호텔, 게스트 하우스, 저택, 아파트, ... "
@hoon25 hoon25 linked a pull request Aug 2, 2022 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment