Jeffery
f44200f543
- 導入 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 群組冒煙測試無回歸。
66 lines
1.5 KiB
Markdown
66 lines
1.5 KiB
Markdown
# prisma migrate status
|
|
|
|
Checks the status of your database migrations.
|
|
|
|
## Command
|
|
|
|
```bash
|
|
prisma migrate status [options]
|
|
```
|
|
|
|
## What It Does
|
|
|
|
- Connects to the database
|
|
- Checks the `_prisma_migrations` table
|
|
- Compares applied migrations with local migration files
|
|
- Reports:
|
|
- **Status**: Database is up-to-date or behind
|
|
- **Unapplied migrations**: Count of pending migrations
|
|
- **Missing migrations**: Migrations present in DB but missing locally
|
|
- **Failed migrations**: Any migrations that failed to apply
|
|
|
|
## Options
|
|
|
|
| Option | Description |
|
|
|--------|-------------|
|
|
| `--schema` | Path to schema file |
|
|
| `--config` | Custom path to your Prisma config file |
|
|
|
|
## Examples
|
|
|
|
### Check status
|
|
|
|
```bash
|
|
prisma migrate status
|
|
```
|
|
|
|
Output example (Up to date):
|
|
```
|
|
Database schema is up to date!
|
|
```
|
|
|
|
Output example (Pending):
|
|
```
|
|
Following migration have not yet been applied:
|
|
20240115120000_add_user
|
|
|
|
To apply migrations in development, run:
|
|
prisma migrate dev
|
|
|
|
To apply migrations in production, run:
|
|
prisma migrate deploy
|
|
```
|
|
|
|
## When to Use
|
|
|
|
- **Debugging**: Why is `migrate dev` complaining about drift?
|
|
- **CI/CD**: Verify database state before deploying
|
|
- **Production**: Check if migrations are needed (`migrate deploy`) or if a deployment failed
|
|
|
|
## Exit Codes
|
|
|
|
- `0`: Success (may have pending migrations, but command ran successfully)
|
|
- `1`: Error
|
|
|
|
To check for pending migrations programmatically, you might need to parse the output or use `migrate diff` with exit code flags.
|