Skip to content

fix: english_name UK 제거#771

Merged
whqtker merged 2 commits into
developfrom
fix/host-university-composite-unique
Jun 18, 2026
Merged

fix: english_name UK 제거#771
whqtker merged 2 commits into
developfrom
fix/host-university-composite-unique

Conversation

@whqtker

@whqtker whqtker commented Jun 18, 2026

Copy link
Copy Markdown
Member

관련 이슈

작업 내용

english_name 에 대한 UK 설정 삭제합니다.

특이 사항

리뷰 요구사항 (선택)

@whqtker whqtker self-assigned this Jun 18, 2026
@whqtker whqtker requested a review from Gyuhyeok99 as a code owner June 18, 2026 07:26
@whqtker whqtker added the 버그 Something isn't working label Jun 18, 2026
@coderabbitai

coderabbitai Bot commented Jun 18, 2026

Copy link
Copy Markdown

Review Change Stack

Walkthrough

  1. DB 마이그레이션 변경

    • V52__add_unique_constraint_to_host_university_english_name.sql에서 english_name에 대한 유니크 제약(uk_host_university_english_name) 추가 구문이 삭제되었습니다.
  2. JPA 엔티티 변경

    • HostUniversity.englishName 필드의 @Column에서 unique = true가 제거되고, nullable = falselength = 200만 유지됩니다.
  3. 레포지토리 메서드 교체

    • HostUniversityRepository에서 findByEnglishName이 삭제되고 findByKoreanName이 추가되었습니다.
  4. 서비스 검증 로직 제거

    • AdminHostUniversityServicecreateHostUniversity에서 validateEnglishNameNotExists(...) 호출과 해당 private 메서드가 삭제되었습니다.
    • updateHostUniversity에서 validateEnglishNameNotDuplicated(...) 호출과 해당 private 메서드가 삭제되었습니다.
  5. 테스트 케이스 전환

    • 기존에 englishName 중복 시 예외를 기대하던 생성/수정 테스트가 성공 케이스로 변경되었습니다.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Suggested reviewers

  • wibaek
  • lsy1307
  • Hexeong
  • JAEHEE25
  • sukangpunch
  • Gyuhyeok99
🚥 Pre-merge checks | ✅ 2 | ❌ 3

❌ Failed checks (3 warnings)

Check name Status Explanation Resolution
Linked Issues check ⚠️ Warning PR 목표와 실제 구현 사이에 불일치가 존재합니다. 이슈 #770은 영문명 UK 설정에 따른 애플리케이션 기동 실패를 해결하도록 요청하나, 현 PR은 영문명 UK를 완전히 제거하고 있습니다. 이슈 #770에서 제시한 요구사항(복합 UK 또는 제약 완화)이 이 PR의 변경으로 적절히 해결되는지 재검토하고 명확히 해 주세요.
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
Description check ⚠️ Warning PR 설명이 불완전합니다. 작업 내용이 간단한 한 줄 설명만 있고, 특이 사항과 리뷰 요구사항이 채워지지 않았습니다. 작업 내용을 더 상세히 설명하고 (UK 제약 제거 이유, 영향 범위 등), 데이터베이스 마이그레이션 및 코드 변경 관련 특이사항을 작성하세요.
✅ Passed checks (2 passed)
Check name Status Explanation
Title check ✅ Passed PR 제목 'fix: english_name UK 제거'는 변경사항의 핵심 내용을 명확하게 요약하고 있으며, 파일 목록이나 모호한 표현 없이 간결합니다.
Out of Scope Changes check ✅ Passed 모든 변경 사항이 english_name UK 제거라는 단일 목표에 일관되게 초점을 맞추고 있으며, 범위를 벗어난 변경은 없습니다.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/host-university-composite-unique

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 846fac3a95

ℹ️ 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".

@whqtker whqtker changed the title refactor: (english_name, korean_name) 조합으로 UK 설정하도록 fix: english_name UK 제거 Jun 18, 2026

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick comments (1)
src/test/java/com/example/solidconnection/admin/service/AdminHostUniversityServiceTest.java (1)

279-285: ⚡ Quick win

1) 성공 케이스 전환은 좋고, 저장 상태 검증까지 추가하면 회귀 방지가 더 단단해집니다.

두 테스트 모두 응답 DTO만 확인하고 있어, 나중에 서비스가 조회/매핑 방식으로 바뀌면 의도와 다른 동작도 통과할 수 있습니다. create는 신규 ID 생성/레코드 수 증가(또는 중복 englishName 행 존재), update는 DB 재조회 후 englishName 반영까지 함께 검증해 주세요.

Also applies to: 389-395

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In
`@src/test/java/com/example/solidconnection/admin/service/AdminHostUniversityServiceTest.java`
around lines 279 - 285, The test cases for createHostUniversity and
updateHostUniversity (the second location at lines 389-395) are only validating
the response DTO but not verifying that the data was actually persisted to the
database. Enhance both tests by adding persistence verification: for
createHostUniversity, verify that a new ID was generated and the database record
count increased (or query to confirm the new record exists with the provided
englishName); for updateHostUniversity, re-query the database after the update
call and verify that the englishName field was actually persisted with the
updated value. This ensures the service correctly saves changes and prevents
regressions if the implementation is refactored to return mapped DTOs without
persisting them.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In
`@src/test/java/com/example/solidconnection/admin/service/AdminHostUniversityServiceTest.java`:
- Around line 279-285: The test cases for createHostUniversity and
updateHostUniversity (the second location at lines 389-395) are only validating
the response DTO but not verifying that the data was actually persisted to the
database. Enhance both tests by adding persistence verification: for
createHostUniversity, verify that a new ID was generated and the database record
count increased (or query to confirm the new record exists with the provided
englishName); for updateHostUniversity, re-query the database after the update
call and verify that the englishName field was actually persisted with the
updated value. This ensures the service correctly saves changes and prevents
regressions if the implementation is refactored to return mapped DTOs without
persisting them.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 3bb91340-5fcf-49bf-b9a7-0f2be2951736

📥 Commits

Reviewing files that changed from the base of the PR and between f0acacb and ce3af62.

📒 Files selected for processing (6)
  • src/main/java/com/example/solidconnection/admin/university/service/AdminHostUniversityService.java
  • src/main/java/com/example/solidconnection/university/domain/HostUniversity.java
  • src/main/java/com/example/solidconnection/university/repository/HostUniversityRepository.java
  • src/main/resources/db/migration/V52__add_unique_constraint_to_host_university_english_name.sql
  • src/main/resources/db/migration/V52__extend_univ_apply_info_import_columns.sql
  • src/test/java/com/example/solidconnection/admin/service/AdminHostUniversityServiceTest.java
💤 Files with no reviewable changes (3)
  • src/main/resources/db/migration/V52__add_unique_constraint_to_host_university_english_name.sql
  • src/main/java/com/example/solidconnection/admin/university/service/AdminHostUniversityService.java
  • src/main/java/com/example/solidconnection/university/repository/HostUniversityRepository.java

@whqtker whqtker added the 진행 중 자유롭게 merge 가능 label Jun 18, 2026
@whqtker whqtker merged commit 443665f into develop Jun 18, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

버그 Something isn't working 진행 중 자유롭게 merge 가능

Projects

None yet

Development

Successfully merging this pull request may close these issues.

fix: english_name UK 설정에 따른 애플리케이션 기동 실패 해결

1 participant