Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add rules/prisma/prisma-next/test-database-limitationsgit clone --depth 1 https://github.com/prisma/prisma-nextWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/rules/prisma/prisma-next/test-database-limitations)<a href="https://agentmods.dev/rules/prisma/prisma-next/test-database-limitations"><img src="https://agentmods.dev/badge/rules/prisma/prisma-next/test-database-limitations.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00000 | $0.00901 |
| Opus 5 | $0.00000 | $0.00451 |
| Sonnet 5 | $0.00000 | $0.00180 |
| Haiku 4.5 | $0.00000 | $0.00090 |
Grade A, and why
test-database-limitations scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
This is a copy
97% identical to test-database-limitations — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Database Limitations
Overview
Test databases created via withDevDatabase() from @prisma-next/test-utils use pglite (an in-memory PostgreSQL implementation via @prisma/dev). Pglite does not support PostgreSQL extensions like pgvector, pg_trgm, etc.
The Problem
When writing tests that use features requiring PostgreSQL extensions:
❌ WRONG: Trying to use extensions in pglite
await withClient(connectionString, async (client) => {
await client.query('create extension if not exists vector'); // ❌ Fails: extension not available
await client.query('create table post (embedding vector(1536))'); // ❌ Fails: vector type doesn't exist
});
Error: extension "vector" is not available or type "vector" does not exist
Solutions
Option 1: Avoid Extension Features in Tests (Recommended for Non-Extension Tests)
If your test is not specifically testing extension functionality, avoid selecting or using extension-dependent columns:
✅ CORRECT: Don't select extension columns in non-extension tests
// Test is about ORM includes, not vector operations
const plan = orm
.user()
.include.posts((child) =>
child
.select((m) => ({
id: m.id,
title: m.title,
createdAt: m.createdAt,
// ✅ Don't select embedding - test is about includes, not vectors
}))
)
.select((u) => ({ id: u.id, posts: true }))
.findMany();
Why? The test focuses on the feature being tested (includes), not the extension functionality. Extension functionality should be tested separately.
Option 2: Use Real PostgreSQL Database
If you must test extension functionality, use a real PostgreSQL database instead of withDevDatabase():
✅ CORRECT: Use real PostgreSQL for extension tests
// Connect to real PostgreSQL database (not pglite)
const connectionString = process.env['DATABASE_URL']; // Real PostgreSQL
const client = new Client({ connectionString });
await client.connect();
try {
await client.query('create extension if not exists vector');
await client.query('create table post (embedding vector(1536))');
// ... test extension functionality
} finally {
await client.end();
}
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- yesterday First seen · 108 lines · 0 tokens per session scan A 2e257c0423d9
test-database-limitations is a cursor rule published in the GitHub repository prisma/prisma-next (419 stars, last pushed 10d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 901 tokens. A static security scan graded it A with 0 findings. It is 97% identical to test-database-limitations, differing in 4 lines, and is treated as a copy.
Other cursor rules, from other repositories
postgres-lateral-patterns
PostgreSQL LATERAL and jsonagg rendering patterns.
sql-orm-client-whole-shape-assertions
Prefer whole-result-shape assertions with explicit select projections in sql-orm-client tests.
sql-queries-not-asts
Name built-and-lowered SQL units "queries", not "asts".
sql-types-imports
Canonical import paths for SQL types.
storage-type-hooks
Use codec-owned storage-type hooks for control-plane type behavior.
test-database-limitations
Test databases created via withDevDatabase() from @repo/test-utils use pglite (an in-memory PostgreSQL implementation via @prisma/dev). Pglite does not support PostgreSQL extensions like pgvector, pgtrgm, etc.