[Fix] Migrate SQL for Avoiding to confilct

[Kong-TaeHyeon]

Summary by CodeRabbit

릴리스 노트

• 개선 사항
  • 데이터베이스 마이그레이션 안정성을 강화했습니다. 테이블, 인덱스 및 제약 조건 생성 과정을 개선하여 반복된 실행 시에도 오류가 발생하지 않도록 설정했습니다. 이를 통해 데이터베이스 초기화가 더욱 안정적이고 신뢰할 수 있게 되었습니다.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

참고 자료

노트

[coderabbitai]

Walkthrough

데이터베이스 마이그레이션 파일 V1__create_tables.sql의 모든 CREATE TABLE, CREATE INDEX, ALTER TABLE ADD CONSTRAINT 문에 "IF NOT EXISTS" 절을 추가합니다. 이 변경을 통해 마이그레이션을 반복 실행할 때 발생하는 오류를 방지하며, 마이그레이션의 멱등성을 보장합니다.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3분

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The PR description only contains template placeholders with no substantive information about the changes, objectives, or rationale for the SQL migration modifications.	Add detailed description explaining why IF NOT EXISTS clauses were added, what problems this solves, and any migration implications or testing performed.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title mentions fixing migration SQL to avoid conflicts, which aligns with the actual changes (adding IF NOT EXISTS clauses), but contains a typo ('confilct' instead of 'conflict') and is somewhat vague about the specific fix.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix/migrate-create

---

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 8ae8503 and 8278ab6.

📒 Files selected for processing (1)

• src/main/resources/db/migration/V1__create_tables.sql

🧰 Additional context used

📓 Path-based instructions (1)

**/*.sql

⚙️ CodeRabbit configuration file

**/*.sql: As a team convention, we do not specify FK constraints. Please avoid suggesting adding FK constraints in code reviews. For columns used as primary keys (PK) or foreign keys (FK), follow the "bigint" type convention. If a column name is "id" or ends with "_id" but is not "bigint", raise a warning with prefix 🚨.

Files:

• src/main/resources/db/migration/V1__create_tables.sql

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: test

🔇 Additional comments (2)

src/main/resources/db/migration/V1__create_tables.sql (2)

1-479: ID column type convention을 올바르게 준수했습니다.

모든 primary key와 foreign key column이 bigint type을 사용하고 있습니다.

---

1-479: Team convention을 준수하여 FK constraint를 정의하지 않았습니다.

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[github-actions]

Test results

753 tests   753 ✅  15s ⏱️
222 suites    0 💤
222 files      0 ❌

Results for commit 8278ab6.

[coderabbitai]

Actionable comments posted: 0

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

src/main/resources/db/migration/V1__create_tables.sql (1)

1-479: Versioned migration에서 IF NOT EXISTS 사용은 anti-pattern입니다.

Flyway는 적용된 마이그레이션을 tracking하여 중복 실행을 방지합니다. IF NOT EXISTS를 추가하면:

• Migration version tracking이 무의미해집니다
• 기존 schema와 정의가 다를 경우 변경사항이 적용되지 않습니다
• Schema drift를 감지할 수 없습니다

이 패턴은 초기 bootstrap migration인 V1에서 특히 문제가 됩니다. 올바른 접근은 Flyway의 baseline 기능을 사용하거나 깨끗한 환경에서 마이그레이션을 실행하는 것입니다. IF NOT EXISTS를 제거하고 schema 충돌의 근본 원인을 해결하시기 바랍니다.

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 8ae8503 and 8278ab6.

📒 Files selected for processing (1)

• src/main/resources/db/migration/V1__create_tables.sql

🧰 Additional context used

📓 Path-based instructions (1)

**/*.sql

⚙️ CodeRabbit configuration file

**/*.sql: As a team convention, we do not specify FK constraints. Please avoid suggesting adding FK constraints in code reviews. For columns used as primary keys (PK) or foreign keys (FK), follow the "bigint" type convention. If a column name is "id" or ends with "_id" but is not "bigint", raise a warning with prefix 🚨.

Files:

• src/main/resources/db/migration/V1__create_tables.sql

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: test

🔇 Additional comments (2)

src/main/resources/db/migration/V1__create_tables.sql (2)

1-479: ID column type convention을 올바르게 준수했습니다.

모든 primary key와 foreign key column이 bigint type을 사용하고 있습니다.

---

1-479: Team convention을 준수하여 FK constraint를 정의하지 않았습니다.