- 導入 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 群組冒煙測試無回歸。
3.6 KiB
Schema Changes
Prisma v7 promotes prisma-client to the default generator. Update your generator block, output path, and imports accordingly.
This guide is for projects that are actually migrating to Prisma 7. Do not apply these schema changes to MongoDB projects; keep those on Prisma 6.x.
Generator Block (v7)
generator client {
provider = "prisma-client"
output = "../generated/prisma"
}
Key Changes
1. Provider name
Use prisma-client in Prisma v7. The older prisma-client-js generator still exists in the repo for legacy setups, but prisma-client is the default path for current projects.
2. Output is required
The output field is mandatory when using prisma-client. Prisma Client no longer generates to node_modules with this generator.
generator client {
provider = "prisma-client"
output = "../generated/prisma"
}
3. engineType changed
Legacy Rust engine settings are gone. With prisma-client, the relevant value is engineType = "client" if you want to state it explicitly, although it is typically inferred and can be omitted.
generator client {
provider = "prisma-client"
output = "../generated/prisma"
engineType = "client"
}
4. moduleFormat is explicit when needed
If you must stay on CommonJS:
generator client {
provider = "prisma-client"
output = "../generated/prisma"
moduleFormat = "cjs"
}
Example Output Paths
Standard project
output = "../generated/prisma"
Creates files like:
generated/prisma/
client.ts
browser.ts
enums.ts
models.ts
models/
Monorepo
output = "../../packages/database/generated/prisma"
Same directory as schema
output = "./generated/prisma"
Creates: prisma/generated/prisma/client.ts
Datasource Block
The url, directUrl, and shadowDatabaseUrl fields in the datasource block are deprecated in Prisma v7. Move them to prisma.config.ts and keep only the provider in schema.prisma:
datasource db {
provider = "postgresql"
}
export default defineConfig({
datasource: {
url: env('DATABASE_URL'),
directUrl: env('DIRECT_URL'),
shadowDatabaseUrl: env('SHADOW_DATABASE_URL'),
},
})
After Schema Changes
-
Run
prisma generate:npx prisma generate -
Update imports throughout your codebase:
import { PrismaClient } from '../generated/prisma/client' -
Update
.gitignoreif you manage this manually:/generated/prisma -
Replace
Prisma.validator()with TypeScriptsatisfieswhen usingprisma-client:import { Prisma } from '../generated/prisma/client' const userSelect = { id: true, email: true, } satisfies Prisma.UserSelect
Generated Entrypoints
client- server-side Prisma Client and Prisma namespacebrowser- browser-safe types and enums without a realPrismaClientenums- slim enum-only entrypointmodels- model types and derived helper types
Preview Features
Preview features still work as before:
generator client {
provider = "prisma-client"
output = "../generated/prisma"
previewFeatures = ["relationJoins", "fullTextSearch"]
}
Recent preview-feature examples also include partialIndexes for PostgreSQL, SQLite, SQL Server, and CockroachDB:
generator client {
provider = "prisma-client"
output = "../generated/prisma"
previewFeatures = ["partialIndexes"]
}