skills
This commit is contained in:
@@ -0,0 +1,89 @@
|
||||
# CockroachDB Setup
|
||||
|
||||
Configure Prisma with CockroachDB.
|
||||
|
||||
## Prerequisites
|
||||
|
||||
- CockroachDB cluster
|
||||
|
||||
## 1. Schema Configuration
|
||||
|
||||
In `prisma/schema.prisma`:
|
||||
|
||||
```prisma
|
||||
datasource db {
|
||||
provider = "cockroachdb"
|
||||
}
|
||||
|
||||
generator client {
|
||||
provider = "prisma-client"
|
||||
output = "../generated"
|
||||
}
|
||||
```
|
||||
|
||||
## 2. Config Configuration (v7)
|
||||
|
||||
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="postgresql://user:password@host:26257/db?sslmode=verify-full"
|
||||
```
|
||||
|
||||
Note: CockroachDB uses the PostgreSQL wire protocol, so the URL often looks like postgresql, but the provider **MUST** be `cockroachdb` in the schema to handle specific CRDB features correctly.
|
||||
|
||||
## Driver Adapter (Prisma ORM 7 required)
|
||||
|
||||
Prisma ORM 7 uses the query compiler by default, so you must use a driver adapter. CockroachDB is PostgreSQL-compatible, so use the PostgreSQL adapter.
|
||||
|
||||
1. Install adapter and driver:
|
||||
```bash
|
||||
npm install @prisma/adapter-pg pg
|
||||
```
|
||||
|
||||
2. Instantiate Prisma Client with the adapter:
|
||||
```typescript
|
||||
import 'dotenv/config'
|
||||
import { PrismaClient } from '../generated/client'
|
||||
import { PrismaPg } from '@prisma/adapter-pg'
|
||||
|
||||
const adapter = new PrismaPg({ connectionString: process.env.DATABASE_URL })
|
||||
const prisma = new PrismaClient({ adapter })
|
||||
```
|
||||
|
||||
## ID Generation
|
||||
|
||||
CockroachDB uses `BigInt` or `UUID` for IDs efficiently.
|
||||
|
||||
```prisma
|
||||
model User {
|
||||
id BigInt @id @default(autoincrement()) // Uses unique_rowid()
|
||||
}
|
||||
```
|
||||
|
||||
Or using string UUIDs:
|
||||
|
||||
```prisma
|
||||
model User {
|
||||
id String @id @default(dbgenerated("gen_random_uuid()")) @db.Uuid
|
||||
}
|
||||
```
|
||||
|
||||
## Common Issues
|
||||
|
||||
### Schema Introspection
|
||||
Always use `provider = "cockroachdb"` to ensure correct type mapping during `db pull`.
|
||||
72
.agents/skills/prisma-database-setup/references/mongodb.md
Normal file
72
.agents/skills/prisma-database-setup/references/mongodb.md
Normal file
@@ -0,0 +1,72 @@
|
||||
# MongoDB Setup
|
||||
|
||||
**⚠️ WARNING: MongoDB is NOT supported in Prisma ORM v7.**
|
||||
|
||||
Support for MongoDB is planned for a future v7 release. If you need MongoDB, you must use **Prisma ORM v6**.
|
||||
|
||||
## Prerequisites
|
||||
|
||||
- MongoDB 4.2+
|
||||
- Replica Set configured (required for transactions)
|
||||
- **Prisma ORM v6.x**
|
||||
|
||||
## 1. Schema Configuration (v6)
|
||||
|
||||
In `prisma/schema.prisma`:
|
||||
|
||||
```prisma
|
||||
datasource db {
|
||||
provider = "mongodb"
|
||||
url = env("DATABASE_URL")
|
||||
}
|
||||
|
||||
generator client {
|
||||
provider = "prisma-client-js"
|
||||
}
|
||||
```
|
||||
|
||||
### ID Field Requirement
|
||||
|
||||
MongoDB models **must** have a mapped `_id` field using `@id` and `@map("_id")`, usually of type `String` with `auto()` and `db.ObjectId`.
|
||||
|
||||
```prisma
|
||||
model User {
|
||||
id String @id @default(auto()) @map("_id") @db.ObjectId
|
||||
email String @unique
|
||||
name String?
|
||||
}
|
||||
```
|
||||
|
||||
### Relations
|
||||
|
||||
Relations in MongoDB expect IDs to be `db.ObjectId` type.
|
||||
|
||||
```prisma
|
||||
model Post {
|
||||
id String @id @default(auto()) @map("_id") @db.ObjectId
|
||||
author User @relation(fields: [authorId], references: [id])
|
||||
authorId String @db.ObjectId
|
||||
}
|
||||
```
|
||||
|
||||
## 2. Environment Variable
|
||||
|
||||
In `.env`:
|
||||
|
||||
```env
|
||||
DATABASE_URL="mongodb+srv://user:password@cluster.mongodb.net/mydb?retryWrites=true&w=majority"
|
||||
```
|
||||
|
||||
## Migrations vs Introspection
|
||||
|
||||
- **No Migrations**: MongoDB is schema-less. `prisma migrate` commands **do not work**.
|
||||
- **db push**: Use `prisma db push` to sync indexes and constraints.
|
||||
- **db pull**: Use `prisma db pull` to generate schema from existing data (sampling).
|
||||
|
||||
## Common Issues
|
||||
|
||||
### "Transactions not supported"
|
||||
Ensure your MongoDB instance is a **Replica Set**. Standalone instances do not support transactions. Atlas clusters are replica sets by default.
|
||||
|
||||
### "Invalid ObjectID"
|
||||
Ensure fields referencing IDs are decorated with `@db.ObjectId` if the target is an ObjectID.
|
||||
109
.agents/skills/prisma-database-setup/references/mysql.md
Normal file
109
.agents/skills/prisma-database-setup/references/mysql.md
Normal file
@@ -0,0 +1,109 @@
|
||||
# MySQL Setup
|
||||
|
||||
Configure Prisma with MySQL (or MariaDB).
|
||||
|
||||
## Prerequisites
|
||||
|
||||
- MySQL or MariaDB database
|
||||
- Connection string
|
||||
|
||||
## 1. Schema Configuration
|
||||
|
||||
In `prisma/schema.prisma`:
|
||||
|
||||
```prisma
|
||||
datasource db {
|
||||
provider = "mysql"
|
||||
}
|
||||
|
||||
generator client {
|
||||
provider = "prisma-client"
|
||||
output = "../generated"
|
||||
}
|
||||
```
|
||||
|
||||
## 2. Config Configuration (v7)
|
||||
|
||||
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="mysql://user:password@localhost:3306/mydb"
|
||||
```
|
||||
|
||||
### Connection String Format
|
||||
|
||||
```
|
||||
mysql://USER:PASSWORD@HOST:PORT/DATABASE
|
||||
```
|
||||
|
||||
- **USER**: Database user
|
||||
- **PASSWORD**: Password
|
||||
- **HOST**: Hostname
|
||||
- **PORT**: Port (default 3306)
|
||||
- **DATABASE**: Database name
|
||||
|
||||
## Driver Adapter (Prisma ORM 7 required)
|
||||
|
||||
Prisma ORM 7 uses the query compiler by default, so you must use a driver adapter.
|
||||
|
||||
1. Install adapter and driver:
|
||||
```bash
|
||||
npm install @prisma/adapter-mariadb mariadb
|
||||
```
|
||||
|
||||
2. Instantiate Prisma Client with the adapter:
|
||||
```typescript
|
||||
import 'dotenv/config'
|
||||
import { PrismaClient } from '../generated/client'
|
||||
import { PrismaMariaDb } from '@prisma/adapter-mariadb'
|
||||
|
||||
const adapter = new PrismaMariaDb({
|
||||
host: 'localhost',
|
||||
port: 3306,
|
||||
connectionLimit: 5,
|
||||
user: process.env.MYSQL_USER,
|
||||
password: process.env.MYSQL_PASSWORD,
|
||||
database: process.env.MYSQL_DATABASE,
|
||||
})
|
||||
|
||||
const prisma = new PrismaClient({ adapter })
|
||||
```
|
||||
|
||||
## PlanetScale Setup
|
||||
|
||||
PlanetScale uses MySQL but requires specific settings because it doesn't support foreign key constraints.
|
||||
|
||||
In `prisma/schema.prisma`:
|
||||
|
||||
```prisma
|
||||
datasource db {
|
||||
provider = "mysql"
|
||||
relationMode = "prisma" // Emulate foreign keys in Prisma
|
||||
}
|
||||
```
|
||||
|
||||
## Common Issues
|
||||
|
||||
### "Too many connections"
|
||||
MySQL has a connection limit. Adjust connection pool size in URL:
|
||||
```env
|
||||
DATABASE_URL="mysql://...?connection_limit=5"
|
||||
```
|
||||
|
||||
### JSON Support
|
||||
MySQL 5.7+ supports JSON. MariaDB 10.2+ supports JSON (as an alias for LONGTEXT with check constraints). Prisma handles this, but verify your version.
|
||||
@@ -0,0 +1,92 @@
|
||||
# PostgreSQL Setup
|
||||
|
||||
Configure Prisma with PostgreSQL.
|
||||
|
||||
## Prerequisites
|
||||
|
||||
- PostgreSQL database (local or cloud)
|
||||
- Connection string
|
||||
|
||||
## 1. Schema Configuration
|
||||
|
||||
In `prisma/schema.prisma`:
|
||||
|
||||
```prisma
|
||||
datasource db {
|
||||
provider = "postgresql"
|
||||
}
|
||||
|
||||
generator client {
|
||||
provider = "prisma-client"
|
||||
output = "../generated"
|
||||
}
|
||||
```
|
||||
|
||||
## 2. Config Configuration (v7)
|
||||
|
||||
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="postgresql://user:password@localhost:5432/mydb?schema=public"
|
||||
```
|
||||
|
||||
### Connection String Format
|
||||
|
||||
```
|
||||
postgresql://USER:PASSWORD@HOST:PORT/DATABASE?schema=SCHEMA
|
||||
```
|
||||
|
||||
- **USER**: Database user
|
||||
- **PASSWORD**: Password (URL encoded if special chars)
|
||||
- **HOST**: Hostname (localhost, IP, or domain)
|
||||
- **PORT**: Port (default 5432)
|
||||
- **DATABASE**: Database name
|
||||
- **SCHEMA**: Schema name (default `public`)
|
||||
|
||||
## Driver Adapter (Prisma ORM 7 required)
|
||||
|
||||
Prisma ORM 7 uses the query compiler by default, so you must use a driver adapter.
|
||||
|
||||
1. Install adapter and driver:
|
||||
```bash
|
||||
npm install @prisma/adapter-pg pg
|
||||
```
|
||||
|
||||
2. Instantiate Prisma Client with the adapter:
|
||||
```typescript
|
||||
import 'dotenv/config'
|
||||
import { PrismaClient } from '../generated/client'
|
||||
import { PrismaPg } from '@prisma/adapter-pg'
|
||||
|
||||
const adapter = new PrismaPg({ connectionString: process.env.DATABASE_URL })
|
||||
const prisma = new PrismaClient({ adapter })
|
||||
```
|
||||
|
||||
## Common Issues
|
||||
|
||||
### "Can't reach database server"
|
||||
- Check host and port
|
||||
- Check firewall settings
|
||||
- Ensure database is running
|
||||
|
||||
### "Authentication failed"
|
||||
- Check user/password
|
||||
- Special characters in password must be URL-encoded
|
||||
|
||||
### "Schema does not exist"
|
||||
- Ensure `?schema=public` (or your schema) is in the URL
|
||||
@@ -0,0 +1,47 @@
|
||||
# Prisma Client Setup
|
||||
|
||||
Generate and instantiate Prisma Client for any database provider.
|
||||
|
||||
## 1. Install dependencies
|
||||
|
||||
```bash
|
||||
npm install prisma --save-dev
|
||||
npm install @prisma/client
|
||||
```
|
||||
|
||||
## 2. Add generator block
|
||||
|
||||
In `prisma/schema.prisma`:
|
||||
|
||||
```prisma
|
||||
generator client {
|
||||
provider = "prisma-client"
|
||||
output = "../generated"
|
||||
}
|
||||
```
|
||||
|
||||
Prisma v7 requires an explicit `output` path and will not generate into `node_modules` by default.
|
||||
|
||||
## 3. Generate Prisma Client
|
||||
|
||||
```bash
|
||||
npx prisma generate
|
||||
```
|
||||
|
||||
Re-run `prisma generate` after every schema change to keep the client in sync.
|
||||
|
||||
## 4. Instantiate Prisma Client
|
||||
|
||||
```typescript
|
||||
import { PrismaClient } from '../generated/client'
|
||||
import { PrismaPg } from '@prisma/adapter-pg'
|
||||
|
||||
const adapter = new PrismaPg({ connectionString: process.env.DATABASE_URL })
|
||||
const prisma = new PrismaClient({ adapter })
|
||||
```
|
||||
|
||||
If you change the generator `output`, update the import path to match. In Prisma ORM 7, a **driver adapter is required** — replace `PrismaPg` with the adapter for your database.
|
||||
|
||||
## 5. Use a single instance
|
||||
|
||||
Each `PrismaClient` instance creates a connection pool. Reuse a single instance per app process to avoid exhausting database connections.
|
||||
@@ -0,0 +1,90 @@
|
||||
# Prisma Postgres Setup
|
||||
|
||||
Configure Prisma with Prisma Postgres (Managed).
|
||||
|
||||
## Overview
|
||||
|
||||
Prisma Postgres is a serverless, managed PostgreSQL database optimized for Prisma.
|
||||
|
||||
## Setup via CLI
|
||||
|
||||
You can provision a Prisma Postgres instance directly via the CLI:
|
||||
|
||||
```bash
|
||||
prisma init --db
|
||||
```
|
||||
|
||||
This will:
|
||||
1. Log you into Prisma Data Platform.
|
||||
2. Create a new project and database instance.
|
||||
3. Update your `.env` with the connection string.
|
||||
|
||||
## Connection String
|
||||
|
||||
The connection string starts with `prisma+postgres://`.
|
||||
|
||||
```env
|
||||
DATABASE_URL="prisma+postgres://api_key@host.prisma-data.net/env_id"
|
||||
```
|
||||
|
||||
## 1. Schema Configuration
|
||||
|
||||
In `prisma/schema.prisma`:
|
||||
|
||||
```prisma
|
||||
datasource db {
|
||||
provider = "postgresql" // Use postgresql provider
|
||||
}
|
||||
|
||||
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'),
|
||||
},
|
||||
})
|
||||
```
|
||||
|
||||
## Driver Adapter (Prisma ORM 7 required)
|
||||
|
||||
Prisma ORM 7 uses the query compiler by default, so you must use a driver adapter. For Prisma Postgres, use the Prisma Postgres serverless driver adapter.
|
||||
|
||||
1. Install adapter and driver:
|
||||
```bash
|
||||
npm install @prisma/adapter-ppg @prisma/ppg
|
||||
```
|
||||
|
||||
2. Use a **direct TCP** connection string for the adapter (from the Prisma Console) and instantiate Prisma Client:
|
||||
```typescript
|
||||
import 'dotenv/config'
|
||||
import { PrismaClient } from '../generated/client'
|
||||
import { PrismaPostgresAdapter } from '@prisma/adapter-ppg'
|
||||
|
||||
const prisma = new PrismaClient({
|
||||
adapter: new PrismaPostgresAdapter({
|
||||
connectionString: process.env.PRISMA_DIRECT_TCP_URL,
|
||||
}),
|
||||
})
|
||||
```
|
||||
|
||||
## Features
|
||||
|
||||
- **Serverless**: Scales to zero.
|
||||
- **Caching**: Integrated query caching (Accelerate).
|
||||
- **Real-time**: Database events (Pulse).
|
||||
|
||||
## Using with Prisma Client
|
||||
|
||||
Since Prisma ORM 7 requires a driver adapter, use the Prisma Postgres adapter shown above when instantiating Prisma Client.
|
||||
106
.agents/skills/prisma-database-setup/references/sqlite.md
Normal file
106
.agents/skills/prisma-database-setup/references/sqlite.md
Normal file
@@ -0,0 +1,106 @@
|
||||
# SQLite Setup
|
||||
|
||||
Configure Prisma with SQLite.
|
||||
|
||||
## Prerequisites
|
||||
|
||||
- None (file-based)
|
||||
|
||||
## 1. Schema Configuration
|
||||
|
||||
In `prisma/schema.prisma`:
|
||||
|
||||
```prisma
|
||||
datasource db {
|
||||
provider = "sqlite"
|
||||
}
|
||||
|
||||
generator client {
|
||||
provider = "prisma-client"
|
||||
output = "../generated"
|
||||
}
|
||||
```
|
||||
|
||||
## 2. Config Configuration (v7)
|
||||
|
||||
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="file:./dev.db"
|
||||
```
|
||||
|
||||
### Connection String Format
|
||||
|
||||
```
|
||||
file:PATH
|
||||
```
|
||||
|
||||
- **PATH**: Relative path to the database file (from `prisma/schema.prisma` location usually, but in v7 check `prisma.config.ts` context). Usually relative to the schema file.
|
||||
|
||||
## Driver Adapter (Prisma ORM 7 required)
|
||||
|
||||
Prisma ORM 7 uses the query compiler by default, so you must use a driver adapter.
|
||||
|
||||
1. Install adapter and driver:
|
||||
```bash
|
||||
npm install @prisma/adapter-better-sqlite3 better-sqlite3
|
||||
```
|
||||
|
||||
2. Instantiate Prisma Client with the adapter:
|
||||
```typescript
|
||||
import { PrismaClient } from '../generated/client'
|
||||
import { PrismaBetterSqlite3 } from '@prisma/adapter-better-sqlite3'
|
||||
|
||||
const adapter = new PrismaBetterSqlite3({
|
||||
url: process.env.DATABASE_URL ?? 'file:./dev.db',
|
||||
})
|
||||
|
||||
const prisma = new PrismaClient({ adapter })
|
||||
```
|
||||
|
||||
## Using Driver Adapter (LibSQL / Turso)
|
||||
|
||||
For edge compatibility or Turso:
|
||||
|
||||
1. Install:
|
||||
```bash
|
||||
npm install @prisma/adapter-libsql @libsql/client
|
||||
```
|
||||
|
||||
2. Instantiate:
|
||||
```typescript
|
||||
import { PrismaClient } from '../generated/client'
|
||||
import { PrismaLibSql } from '@prisma/adapter-libsql'
|
||||
|
||||
const adapter = new PrismaLibSql({
|
||||
url: process.env.TURSO_DATABASE_URL,
|
||||
authToken: process.env.TURSO_AUTH_TOKEN,
|
||||
})
|
||||
const prisma = new PrismaClient({ adapter })
|
||||
```
|
||||
|
||||
## Limitations
|
||||
|
||||
- **No Enums**: SQLite doesn't support enums (Prisma polyfills them or treats as String).
|
||||
- **No Scalar Lists**: `String[]` is not supported directly.
|
||||
- **Concurrency**: Write operations lock the file.
|
||||
|
||||
## Common Issues
|
||||
|
||||
### "Database file not found"
|
||||
Ensure the path in `DATABASE_URL` is correct relative to where Prisma is running or the schema file. `file:./dev.db` creates it next to schema.
|
||||
94
.agents/skills/prisma-database-setup/references/sqlserver.md
Normal file
94
.agents/skills/prisma-database-setup/references/sqlserver.md
Normal file
@@ -0,0 +1,94 @@
|
||||
# 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 (v7)
|
||||
|
||||
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 (Prisma ORM 7 required)
|
||||
|
||||
Prisma ORM 7 uses the query compiler by default, so you must use a driver adapter.
|
||||
|
||||
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.
|
||||
Reference in New Issue
Block a user