feat: 完成 B 群組 — 資料層與核心領域模型
- 導入 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 群組冒煙測試無回歸。
This commit is contained in:
@@ -0,0 +1,80 @@
|
||||
# prisma migrate reset
|
||||
|
||||
Resets your database and re-applies all migrations.
|
||||
|
||||
## Command
|
||||
|
||||
```bash
|
||||
prisma migrate reset [options]
|
||||
```
|
||||
|
||||
## What It Does
|
||||
|
||||
1. **Drops** the database (if possible) or deletes all data/tables
|
||||
2. **Re-creates** the database
|
||||
3. **Applies** all migrations from `prisma/migrations/`
|
||||
4. Stops there - run seed and generate explicitly if needed
|
||||
|
||||
**Warning: All data will be lost.**
|
||||
|
||||
When Prisma detects an AI agent, this command is blocked until the user gives explicit consent. Follow `agent-safety.md`; `--force` skips the ordinary prompt but does not constitute user consent for an agent.
|
||||
|
||||
## Options
|
||||
|
||||
| Option | Description |
|
||||
|--------|-------------|
|
||||
| `--force` / `-f` | Skip confirmation prompt |
|
||||
| `--schema` | Path to schema file |
|
||||
| `--config` | Custom path to your Prisma config file |
|
||||
|
||||
## Examples
|
||||
|
||||
### Basic reset
|
||||
|
||||
```bash
|
||||
prisma migrate reset
|
||||
```
|
||||
|
||||
Prompts for confirmation in interactive terminals.
|
||||
|
||||
### Force reset (CI/Automation)
|
||||
|
||||
```bash
|
||||
prisma migrate reset --force
|
||||
```
|
||||
|
||||
### With custom schema
|
||||
|
||||
```bash
|
||||
prisma migrate reset --schema=./custom/schema.prisma
|
||||
```
|
||||
|
||||
## When to Use
|
||||
|
||||
- **Development**: When you want a fresh start
|
||||
- **Testing**: Resetting test database before suites
|
||||
- **Drift Recovery**: When the database is out of sync and you can't migrate
|
||||
|
||||
## Follow-up Steps
|
||||
|
||||
Run `prisma generate` and `prisma db seed` explicitly when you need refreshed client output or seed data after a reset.
|
||||
|
||||
## Configuration
|
||||
|
||||
Configure the seed script in `prisma.config.ts`, then run it explicitly after reset:
|
||||
|
||||
```typescript
|
||||
export default defineConfig({
|
||||
migrations: {
|
||||
seed: 'tsx prisma/seed.ts',
|
||||
},
|
||||
})
|
||||
```
|
||||
|
||||
Typical workflow:
|
||||
|
||||
```bash
|
||||
prisma migrate reset --force
|
||||
prisma generate
|
||||
prisma db seed
|
||||
```
|
||||
Reference in New Issue
Block a user