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 群組冒煙測試無回歸。
70 lines
2.3 KiB
Markdown
70 lines
2.3 KiB
Markdown
# console-and-connections
|
|
|
|
Use Prisma Console workflows for project visibility, data inspection, and connection setup.
|
|
|
|
## Priority
|
|
|
|
HIGH
|
|
|
|
## Why It Matters
|
|
|
|
Many Prisma Postgres tasks are quickest in the Console: viewing Studio data, checking metrics, and retrieving connection details. This avoids unnecessary API or CLI work for simple operational tasks.
|
|
|
|
## Console workflow
|
|
|
|
1. Open `https://console.prisma.io`.
|
|
2. Select workspace and project.
|
|
3. Use dashboard metrics for usage and billing visibility.
|
|
4. Open the **Studio** tab in the sidebar to inspect and edit data.
|
|
|
|
## Local Studio
|
|
|
|
You can also inspect data locally:
|
|
|
|
```bash
|
|
npx prisma studio
|
|
```
|
|
|
|
## Linking an existing project
|
|
|
|
If the Prisma Postgres database already exists, link the local project instead of provisioning a new one:
|
|
|
|
```bash
|
|
prisma postgres link
|
|
```
|
|
|
|
For CI or non-interactive usage:
|
|
|
|
```bash
|
|
prisma postgres link --api-key "<your-api-key>" --database "db_..."
|
|
```
|
|
|
|
This command updates or creates `.env` with `DATABASE_URL`. If the project is already linked, use `--force` to re-link. After linking, run `prisma generate`, then `prisma migrate dev` if you need to apply the schema.
|
|
|
|
## Connection setup
|
|
|
|
For direct PostgreSQL tools and drivers:
|
|
|
|
- Generate/copy direct connection credentials from the project connection UI.
|
|
- Use the resulting PostgreSQL URL as `DATABASE_URL` for `pg` and `@prisma/adapter-pg`.
|
|
- For Prisma Postgres direct TCP, include `sslmode=require`.
|
|
|
|
Typical direct TCP format:
|
|
|
|
```env
|
|
DATABASE_URL="postgres://identifier:key@db.prisma.io:5432/postgres?sslmode=require"
|
|
```
|
|
|
|
Management API connection responses expose both `endpoints.direct` (`db.prisma.io:5432`) and `endpoints.pooled` (`pooled.db.prisma.io:5432`); prefer those fields over the deprecated flat `connectionString`. Connection secrets are shown once at creation (one-time view); store them immediately.
|
|
|
|
## Adapter choices
|
|
|
|
- Standard Node.js apps: prefer `@prisma/adapter-pg` with the direct TCP URL above.
|
|
- Edge/serverless runtimes: use `@prisma/adapter-ppg` with `@prisma/ppg` only when you specifically need the Prisma Postgres serverless driver.
|
|
|
|
## References
|
|
|
|
- [Prisma Postgres overview](https://www.prisma.io/docs/postgres/introduction/overview)
|
|
- [Viewing data](https://www.prisma.io/docs/postgres/integrations/viewing-data)
|
|
- [Direct connections](https://www.prisma.io/docs/postgres/database/direct-connections)
|