fix: 存在しないConjugationProgressテーブルへのDROPを削除 - #52
Merged
Merged
Conversation
ConjugationProgressはschema.prismaに定義されたことがなく、正規のmigration historyには一度もCREATE TABLEが含まれていない（ローカル環境でのみ存在してい たテーブル）。そのためmigrate deployをmigration historyのみから積み上げた 環境（本番など）で実行すると、存在しないテーブルへのDROPでP3009エラーとなり デプロイがcrashloopしていた。
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
1 participant
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.
Summary
20260914000000_replace_conjugation_progress_with_section_progressmigrationがDROP TABLE "ConjugationProgress"を実行していたが、ConjugationProgressはschema.prismaに定義されたことがなく、正規のmigration historyにも一度もCREATE TABLEが含まれていない（開発時にローカルDBにのみ存在していたテーブル）prisma migrate deployを実行すると、存在しないテーブルへのDROPで失敗（P3009）し、以後のmigrationがブロックされてコンテナがcrashloopしていた（vocabook.utcode.netがno available serverになっていた原因）DROP TABLEとその前後のPRAGMA foreign_keys切り替えを削除し、SectionProgressのCREATE TABLE/INDEXのみ残したTest plan
prod.db（_prisma_migrationsテーブル）に残っている失敗記録をprisma migrate resolve --rolled-back 20260914000000_replace_conjugation_progress_with_section_progressで解消してから再デプロイし、migrate deployが正常に完了することを確認する🤖 Generated with Claude Code