test-database-limitations

test-database-limitations is a cursor rule for Codex from prisma/prisma-next. It costs 0 tokens per session (901 once invoked), scanned A, a copy of test-database-limitations, Apache-2.0.

A set of rules about the limits of PGlite, an in-memory implementation of PostgreSQL used by these test databases. It does not provide PostgreSQL extensions such as pgvector or pg_trgm.

In plain words
What is it for?
It helps decide when to avoid extension-dependent columns, use a real PostgreSQL database, or separate extension-specific tests.
Why use it?
It explains why tests fail when they use database extension features that the test database cannot provide.

Cursor rule for Codex

Install

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.

agentmods
npx agentmods add rules/prisma/prisma-next/test-database-limitations
Clone the repo
git clone --depth 1 https://github.com/prisma/prisma-next

Made for: Codex.

Wrote 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.

agentmods badge for test-database-limitations

README.md
[![agentmods](https://agentmods.dev/badge/rules/prisma/prisma-next/test-database-limitations.svg)](https://agentmods.dev/rules/prisma/prisma-next/test-database-limitations)
Your own site
<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>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 901 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 97% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured yesterday against content hash 2e257c0423d9, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

Origin

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.

.agents/rules/test-database-limitations.mdc · 108 lines

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();
}

Read the full file on GitHub · 108 lines

Changes

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.

  1. yesterday First seen · 108 lines · 0 tokens per session scan A 2e257c0423d9

Subscribe to this mod's changes

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.