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 群組冒煙測試無回歸。
95 lines
2.1 KiB
Markdown
95 lines
2.1 KiB
Markdown
# SQL Server Setup
|
|
|
|
Configure Prisma with Microsoft SQL Server.
|
|
|
|
## Prerequisites
|
|
|
|
- SQL Server 2017, 2019, 2022, or Azure SQL
|
|
- TCP/IP enabled
|
|
|
|
## 1. Schema Configuration
|
|
|
|
In `prisma/schema.prisma`:
|
|
|
|
```prisma
|
|
datasource db {
|
|
provider = "sqlserver"
|
|
}
|
|
|
|
generator client {
|
|
provider = "prisma-client"
|
|
output = "../generated"
|
|
}
|
|
```
|
|
|
|
## 2. Config Configuration
|
|
|
|
In `prisma.config.ts`:
|
|
|
|
```typescript
|
|
import { defineConfig, env } from 'prisma/config'
|
|
|
|
export default defineConfig({
|
|
schema: 'prisma/schema.prisma',
|
|
datasource: {
|
|
url: env('DATABASE_URL'),
|
|
},
|
|
})
|
|
```
|
|
|
|
## 3. Environment Variable
|
|
|
|
In `.env`:
|
|
|
|
```env
|
|
DATABASE_URL="sqlserver://localhost:1433;database=mydb;user=sa;password=Password123;encrypt=true;trustServerCertificate=true"
|
|
```
|
|
|
|
### Connection String Format
|
|
|
|
```
|
|
sqlserver://HOST:PORT;database=DB;user=USER;password=PASS;encrypt=true;trustServerCertificate=true
|
|
```
|
|
|
|
- **encrypt**: Required for Azure (true).
|
|
- **trustServerCertificate**: True for self-signed certs (local dev).
|
|
|
|
## Driver Adapter
|
|
|
|
Use a driver adapter for the standard SQL workflow.
|
|
|
|
1. Install adapter and driver:
|
|
```bash
|
|
npm install @prisma/adapter-mssql mssql
|
|
```
|
|
|
|
2. Instantiate Prisma Client with the adapter:
|
|
```typescript
|
|
import 'dotenv/config'
|
|
import { PrismaClient } from '../generated/client'
|
|
import { PrismaMssql } from '@prisma/adapter-mssql'
|
|
|
|
const adapter = new PrismaMssql({
|
|
server: 'localhost',
|
|
port: 1433,
|
|
database: 'mydb',
|
|
user: process.env.SQLSERVER_USER,
|
|
password: process.env.SQLSERVER_PASSWORD,
|
|
options: {
|
|
encrypt: true,
|
|
trustServerCertificate: true,
|
|
},
|
|
})
|
|
|
|
const prisma = new PrismaClient({ adapter })
|
|
```
|
|
|
|
## Common Issues
|
|
|
|
### "Login failed for user"
|
|
- SQL Server auth vs Windows auth. Prisma typically uses SQL Server authentication (username/password).
|
|
- Ensure TCP/IP is enabled in SQL Server Configuration Manager.
|
|
|
|
### "Table not found" (dbo schema)
|
|
Prisma assumes `dbo` schema by default. If using another schema, update the model or connection string? SQL Server provider mostly sticks to default schema.
|