Repository navigation
[Feat] 회원탈퇴 및 연관 데이터 일괄 정리 구현 - #127
Conversation
- 회원탈퇴 API와 전체 세션 무효화 및 개인 콘텐츠 벌크 삭제 구현 - 유료/무료 잔액 분리 조회와 환불 접수 여부 기반 탈퇴 제한 추가 - 이미지 정리 및 카카오 연결 해제 재시도와 재가입 보상 중복 방지 구현 - 거래 기록 보존·기간 종료 파기 및 V7 마이그레이션과 연동 문서 추가 검증: 전체 테스트 1,005개와 추가 마이그레이션 테스트 1개 통과. MySQL 8.0 격리 DB 보조 테스트 15개, JAR 빌드, MySQL 테스트 컴파일 통과. MySQL 8.4 및 실제 카카오 호출 검증은 미실행.
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
 |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 5418963d69
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| long unfinished=em.createQuery("select count(r) from ImageCleanupRequest r where r.userId=:user and r.status<>:done",Long.class) | ||
| .setParameter("user",userId).setParameter("done",ImageCleanupRequest.Status.COMPLETED).getSingleResult(); | ||
| if(unfinished>0) return false; | ||
| data.deleteAccounting(userId,now()); |
There was a problem hiding this comment.
If an operator reclaims a payment after withdrawal, this purge can delete the new accounting records before their five-year retention period ends. PaymentReclaimer.execute() updates payment_orders.updated_at and inserts a dated payment_credit_reclamations row, but does not extend users.retention_until; only the Spring payment callbacks call retainAccountingRecords(). This is reachable when a READY order is paid and cancelled after withdrawal and subsequently reclaimed. Recompute the latest accounting retention deadline under the user lock before deleting, or extend the stored deadline in the reclamation transaction as well.
Useful? React with 👍 / 👎.
PULL REQUEST
🎋 작업 브랜치
💡 작업동기
🔑 주요 변경사항
🏞 스크린샷 (선택)
💬 리뷰 요구사항 (선택)