eventsテーブルをマイグレーションとして追加#361
Open
TkymHrt wants to merge 1 commit into
Open
Conversation
hikahana
reviewed
Sep 8, 2025
| docker compose exec api hasura metadata apply | ||
| docker compose exec api hasura metadata reload | ||
|
|
||
| db-export: |
Collaborator
There was a problem hiding this comment.
これもしかしてだけどdb-exportのmakeコマンドいらない説ありそう。
先、migrateでup.sql down.sqlが作成されるから今後はmigrateのバージョン管理だけで完結しそう。
一応コメントアウト対応とかがいいかも！
| down: | ||
| docker compose down | ||
|
|
||
| # Apply database migrations first, then metadata to avoid temporary inconsistencies |
| docker compose exec api hasura metadata export | ||
| docker compose exec api hasura migrate create "auto" --from-server --database-name default | ||
|
|
||
| # Production apply order aligned with best practice (migrations first) |
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
2 participants
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.
対応Issue
概要
本番で手動作成された
eventsテーブルを正式なマイグレーションとして管理下に置き、以後の環境差異を防止。併せて Hasura 適用順序を
migrate → metadataに変更し一時的な不整合警告の発生を回避。実装詳細
CREATE TABLE IF NOT EXISTS public.events (...)down.sql:DROP TABLE IF EXISTS public.events;db-apply/db-apply-prodの順序を画面スクリーンショット等
（不要 / なし）
テスト項目
make run後hasura migrate statusで新マイグレーションが Applied{ events { id surveyUrl isSurveyActive } }が 200 / エラーなしeventsが存在する環境（本番）でも再適用時エラーが出ない（IF NOT EXISTS）