- 導入 Prisma 7.9.1 + SQLite(better-sqlite3 driver adapter),prisma.config.ts 管理連線設定 - 完整資料模型:User/Work/Character/CharacterAlias/EpisodicMemory/SemanticMemory/ ProceduralRule/EmotionState/Relationship/SentimentLedgerEntry - packages/db:Prisma Client 存取層(ESM,因 Prisma 7 產出的 generated client 僅支援 ESM) - apps/api 隨之改為 ESM 以相容 packages/db - packages/shared:新增角色/記憶/情緒/關係共用型別,api 與 web 皆從此匯入 - prisma/seed.ts:建立測試使用者與元氣型測試角色,含完整關係帳本與記憶種子資料 - apps/api:新增 GET /characters - scripts/smoke/B.mjs:驗證資料表齊全、API 讀出種子角色、關係與記憶可寫入讀出 - 保留 Prisma 官方隨 CLI 附的 agent skill 文件(.agents/skills 等),供後續群組查閱 npm run restart && npm run smoke -- B 皆通過(B-V),A 群組冒煙測試無回歸。
1.6 KiB
1.6 KiB
prisma migrate resolve
Resolves issues with database migrations, such as failed migrations or baselining.
Command
prisma migrate resolve [options]
What It Does
Updates the _prisma_migrations table to manually change the state of a migration. This is a recovery tool.
Options
You must provide exactly one of --applied or --rolled-back.
| Option | Description |
|---|---|
--applied <name> |
Mark a migration as applied (success) |
--rolled-back <name> |
Mark a migration as rolled back (ignored/failed) |
--schema |
Path to schema file |
--config |
Custom path to your Prisma config file |
Examples
Mark as Applied (Baselining)
If you have existing tables and want to initialize migrations without running the SQL:
prisma migrate resolve --applied 20240101000000_initial_migration
This tells Prisma "Assume this migration has already run".
Mark as Rolled Back (Fixing Failures)
If a migration failed (e.g., syntax error) and you fixed the SQL or want to retry:
prisma migrate resolve --rolled-back 20240115120000_failed_migration
This tells Prisma "Forget this migration run, let me try applying it again".
Use Cases
- Baselining: Adopting Prisma Migrate on an existing production database.
- Failed Migrations: Recovering from a failed
migrate deployin production. - Hotfixes: reconciling manual database changes (rare).