-
Notifications
You must be signed in to change notification settings - Fork 0
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
fix: 회원탈퇴 데이터 삭제 방식 변경 #241
Conversation
@Modifying | ||
@Query( | ||
"UPDATE MissionRecordBoost mrb SET mrb.deletedAt = CURRENT_TIMESTAMP WHERE mrb.member.id = :memberId") | ||
@Query("DELETE FROM MissionRecordBoost mrb WHERE mrb.member.id = :memberId") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
회의때에는 부스터 갯수는 남겨두기로 했던 거 같은데 이렇게하면 부스터도 같이 날아가지않나요?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
넵 맞아용 미션 기록이 지워졌는데 굳이 부스트를 DB에 남길 필요가 없다고 생각했어용
추후 마이그레이션을 진행한다고 가정했을때에도 불필요한 데이터라 생각했습니다
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
음.. 그러면 피드에 뜨는 부스트갯수가 mission_record_boost에서가져오는 것 같은데 지우면 피드에 뜨는 숫자도 줄지않나요?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
아 내부적으로도 이야기 나왔었던 내용이네용
제가 놓쳤습니다..! 삭제 안되도록 수정할게요
Quality Gate passedIssues Measures |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
🌱 관련 이슈
📌 작업 내용
🙏 리뷰 요구사항
📚 레퍼런스