Conversation
- deleteAllInBatch가 FK cascade를 무시하여 Scrap FK 제약 위반으로 500 에러 발생 - 공개 코스 삭제 전 scrapRepository.deleteByPublicCourseIn() 호출 추가
thingineeer
added a commit
that referenced
this pull request
Feb 19, 2026
[Fix] - 공개 코스 삭제 시 Record FK null 처리 추가
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
😶 무슨 이슈인가요?
관리자가 타인의 공개 코스를 삭제할 때 500 Internal Server Error 발생.
deleteAllInBatch가 JPA cascade를 무시하고 직접 SQL DELETE를 실행하여,Scrap테이블의 FK 제약 조건 위반.🤔 어떻게 이슈를 해결했나요?
publicCourseRepository.deleteAllInBatch()호출 전에scrapRepository.deleteByPublicCourseIn(publicCourses)추가ScrapRepository에 정의되어 있던 메서드를 활용 (신규 코드 없음)🤯 주의할 점이 있나요?
deleteAllInBatch는 JPA lifecycle callback과 cascade를 무시하므로 연관 엔티티를 수동으로 먼저 삭제해야 합니다!