database

A set of Rust rules for working with databases, recommending SQLx for PostgreSQL and SQLite. It covers connection pools, migrations, repositories, typed queries, errors, tests, transactions, and performance.

In plain words
What is it for?
Use it when adding database connections, schema migrations, data-access code, queries, transactions, tests, or production database configuration in a Rust project.
Why use it?
It provides a consistent way to design database access and catch query or integration mistakes during development.

Cursor rule for Cursor

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/tyrchen/cursor-rust-rules/database
Clone the repo
git clone --depth 1 https://github.com/tyrchen/cursor-rust-rules

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 3,597 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found 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.03597
Opus 5 $0.00000 $0.01799
Sonnet 5 $0.00000 $0.00719
Haiku 4.5 $0.00000 $0.00360

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

Security

Grade A, and why

database 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 2d ago.

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.

.cursor/rules/rust/features/database.mdc ยท 504 lines

How it starts

The opening of the file, as written. The whole thing โ€” 504 lines โ€” stays where its author put it; the contents beside it link to each section on GitHub.

๐Ÿ—„๏ธ RUST DATABASE BEST PRACTICES

TL;DR: Comprehensive guidelines for database access in Rust using SQLx, focusing on type safety, async patterns, and testing strategies.

๐Ÿ” DATABASE ARCHITECTURE STRATEGY

graph TD
    Start["Database Integration"] --> DBChoice{"Database<br>Type?"}

    DBChoice -->|PostgreSQL| Postgres["PostgreSQL with SQLx"]
    DBChoice -->|SQLite| SQLite["SQLite with SQLx"]
    DBChoice -->|Multiple| MultiDB["Multi-Database Support"]

    Postgres --> ConnectionPool["Connection Pool Setup"]
    SQLite --> ConnectionPool
    MultiDB --> ConnectionPool

    ConnectionPool --> Migrations["Database Migrations"]
    Migrations --> EntityDesign["Entity Design"]

    EntityDesign --> RepositoryPattern["Repository Pattern"]
    RepositoryPattern --> QueryPatterns["Query Patterns"]

    QueryPatterns --> TypeSafety["Type Safety"]
    TypeSafety --> ErrorHandling["Error Handling"]

    ErrorHandling --> Testing["Database Testing"]
    Testing --> Transactions["Transaction Management"]
    Transactions --> Performance["Performance Optimization"]

    Performance --> Production["Production Database"]

    style Start fill:#4da6ff,stroke:#0066cc,color:white
    style ConnectionPool fill:#4dbb5f,stroke:#36873f,color:white
    style RepositoryPattern fill:#ffa64d,stroke:#cc7a30,color:white
    style Testing fill:#d94dbb,stroke:#a3378a,color:white

๐ŸŽฏ DATABASE LIBRARY SELECTION

SQLx as the Standard

  • Always use SQLx - avoid rusqlite, tokio-postgres, or other lower-level libraries
  • Support multiple databases through SQLx's unified interface
  • Leverage compile-time query checking when possible
  • Use async/await patterns for all database operations
# Cargo.toml - SQLx configuration
[dependencies]
sqlx = { version = "0.8", features = [
    "chrono",
    "postgres",
    "runtime-tokio-rustls",
    "sqlite",
    "uuid"
] }

๐Ÿ”ง QUERY PATTERNS

Use sqlx::query_as Instead of Macros

// โœ… Preferred: Use sqlx::query_as with custom types
#[derive(Debug, Clone, sqlx::FromRow, Serialize, Deserialize)]
#[serde(rename_all = "camelCase")]
pub struct User {
    pub id: Uuid,
    pub username: String,
    pub email: String,
    pub created_at: DateTime<Utc>,
    pub updated_at: DateTime<Utc>,
    pub is_active: bool,
}

impl User {
    pub async fn find_by_id(
        pool: &PgPool,
        id: Uuid
    ) -> Result<Option<Self>, sqlx::Error> {
        sqlx::query_as::<_, User>(
            "SELECT id, username, email, created_at, updated_at, is_active
             FROM users
             WHERE id = $1"
        )
        .bind(id)
        .fetch_optional(pool)
        .await
    }

    pub async fn list_active_users(
        pool: &PgPool,
        limit: i64,
        offset: i64,
    ) -> Result<Vec<Self>, sqlx::Error> {
        sqlx::query_as::<_, User>(
            "SELECT id, username, email, created_at, updated_at, is_active
             FROM users
             WHERE is_active = true
             ORDER BY created_at DESC
             LIMIT $1 OFFSET $2"
        )
        .bind(limit)
        .bind(offset)
        .fetch_all(pool)
        .await
    }
}

// โŒ Avoid: sqlx::query! macro (compile-time dependencies)
// let result = sqlx::query!("SELECT * FROM users WHERE id = $1", user_id)
//     .fetch_one(pool)
//     .await?;

Read the full file on GitHub ยท 504 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. 2d ago First seen ยท 504 lines ยท 0 tokens per session scan A a9b5f5f80731

Subscribe to this mod's changes

database is a cursor rule published in the GitHub repository tyrchen/cursor-rust-rules (27 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,597 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.