Skip to content

fix: 누락된 Flyway migration 파일 복구#396

Merged
pooreumjung merged 4 commits into
developfrom
fix/#395-restore-missing-flyway-migrations
Jul 8, 2026
Merged

fix: 누락된 Flyway migration 파일 복구#396
pooreumjung merged 4 commits into
developfrom
fix/#395-restore-missing-flyway-migrations

Conversation

@pooreumjung

@pooreumjung pooreumjung commented Jul 8, 2026

Copy link
Copy Markdown
Member

#️⃣ Issue Number

📝 요약(Summary)

dev 서버가 Flyway migration 검증 실패로 기동되지 않는 문제를 수정했습니다.

dev DB의 flyway_schema_history에는 이미 적용되어 있었지만 코드에서 누락되어 있던 migration 파일들을 복구했습니다.

  • V10__populate_i18n_college.sql
  • V11__populate_i18n_department.sql
  • V12__populate_i18n_partnership_restaurant.sql
  • V14__populate_i18n_partnership_description.sql

기존에 이미 존재하던 값은 다시 수정하지 않도록, 다국어 보정이 필요한 컬럼만 업데이트하도록 정리했습니다.

  • college: name_ja, name_vi
  • department: name_ja, name_vi
  • partnership_restaurant: store_name_ja, store_name_vi
  • partnership: description_ja, description_vi

💬 공유사항 to 리뷰어

Flyway는 DB에 적용된 migration 파일이 코드에서 사라지면 validate 단계에서 서버 기동을 중단합니다. 이번 PR은 DB 이력을 수정하지 않고, 누락된
migration 파일을 복구하는 방향으로 처리했습니다.

기존 dev DB에는 해당 migration들이 이미 적용되어 있으므로, 배포 후 Flyway validation이 정상 통과하는지 확인이 필요합니다.

새로 복구한 SQL 파일의 내용이 기존 적용 당시 파일과 완전히 다르면 checksum mismatch가 발생할 수 있습니다. dev 환경에서 mismatch가 발생하면
flyway repair 필요 여부를 별도로 판단해야 합니다.

✅ PR Checklist

PR이 다음 요구 사항을 충족하는지 확인하세요.

  • 커밋 메시지 컨벤션에 맞게 작성했습니다.
  • 변경 사항에 대한 테스트를 했습니다.(버그 수정/기능에 대한 테스트).

@pooreumjung pooreumjung self-assigned this Jul 8, 2026
@pooreumjung pooreumjung added the fix 고치기 label Jul 8, 2026
@gemini-code-assist

Copy link
Copy Markdown
Contributor

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request addresses a server startup issue caused by missing Flyway migration files that were already applied to the development database. By restoring these files, the application's migration history is synchronized with the database state. Additionally, the PR expands internationalization support by populating localized menu and entity names, and includes minor infrastructure improvements to the build system.

Highlights

  • Flyway Migration Recovery: Restored missing Flyway migration files (V10, V11, V12, V14) to resolve validation failures on the development server.
  • I18n Data Updates: Added localized names (Japanese and Vietnamese) for colleges, departments, partnership restaurants, and snack corner menus.
  • Infrastructure Updates: Updated Gradle configuration to include the foojay-resolver-convention and added local configuration files to .gitignore.
New Features

🧠 You can now enable Memory (public preview) to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize the Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counterproductive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.


Migration files lost in the deep, Database secrets they used to keep. Restored to the code, the server now wakes, Fixing the errors that history makes.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Code Review

이번 풀 리퀘스트는 대학, 학과, 제휴 음식점 및 메뉴의 다국어(일본어, 베트남어, 영어) 번역 데이터를 추가하기 위한 Flyway 마이그레이션 SQL 파일들과 프로젝트 설정 변경 사항을 포함하고 있습니다. 리뷰 결과, SQL 파일 내 주석 문법 오류 및 잘못된 파일 확장자(.sql.sql)가 발견되었으며, SQL 쿼리 내 문자열 리터럴에 줄바꿈이 포함되어 데이터베이스에 불필요한 개행 문자가 저장되는 문제가 여러 군데 존재합니다. 또한, 베트남어 번역 내에 한국어 조사('및')가 잘못 포함된 번역 오류가 있어 이에 대한 수정이 필요합니다.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

Comment thread src/main/resources/db/migration/V17__populate_i18n_menu_name.sql Outdated
Comment thread src/main/resources/db/migration/V11__populate_i18n_department.sql Outdated
Comment thread src/main/resources/db/migration/V11__populate_i18n_department.sql Outdated
Comment thread src/main/resources/db/migration/V11__populate_i18n_department.sql Outdated
Comment thread src/main/resources/db/migration/V11__populate_i18n_department.sql Outdated
Comment thread src/main/resources/db/migration/V11__populate_i18n_department.sql Outdated
Comment thread src/main/resources/db/migration/V11__populate_i18n_department.sql Outdated
Comment thread src/main/resources/db/migration/V11__populate_i18n_department.sql Outdated
Comment thread src/main/resources/db/migration/V11__populate_i18n_department.sql Outdated
Comment thread src/main/resources/db/migration/V11__populate_i18n_department.sql Outdated
@pooreumjung pooreumjung merged commit e556e57 into develop Jul 8, 2026
1 check passed
@pooreumjung pooreumjung deleted the fix/#395-restore-missing-flyway-migrations branch July 8, 2026 16:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

fix 고치기

Projects

None yet

Development

Successfully merging this pull request may close these issues.

fix: Flyway 검증 실패로 인한 dev 서버 기동 오류 수정

1 participant