[FIX] NativeQuery 오작성으로 인한 SQL 호출시 오류가 발생하는 문제 수정#483
Merged
GiJungPark merged 1 commit intodevfrom Mar 29, 2026
Merged
Conversation
- CreatedAt, UpdatedAt 필드가 존재하지 않는데, Native 쿼리에서 해당 필드를 저장하려고 해서 발생하는 문제
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
1 participant
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.
Related Issue
Key Changes
ReadNotification 테이블에는 CreatedAt과 UpdatedAt 필드가 존재하지 않습니다.
하지만 NativeQuery에서 해당 필드를 저장하는 쿼리가 존재하고 있습니다.
이로 인해서, 공지를 읽을 때 읽기 여부를 저장하는 쿼리에서 필드 불일치로 인해 예외가 발생하고 있는 문제였습니다.
따라서, 해당 NativeQuery를 정상적으로 수정하였습니다.
To Reviewers
컴파일 단계에서 문제를 알 수 있는 QueryDSL 등으로의 전환도 고려해봐야 할 듯 싶습니다.
References