Rust Database Layer Delivery

Deliver a migration-compatible, rollback-capable, and observable data access layer based on the actual dialects, schemas, and transaction semantics of databases. Do not treat HTTP handlers as repositories; do not use mocks to validate real database behavior.

Confirming Database Contracts

Before modifications:

• Collect information about the database product, exact version, extensions, deployment topology, read/write nodes;
• Gather current schema constraints, indexes, triggers, views, and migration history;
• Identify locked versions of SQLx, Diesel, SeaORM (or other access stacks) along with their features;
• Determine Rust toolchain/MSRV, synchronous or asynchronous execution models;
• Establish connection limits, instance counts, timeouts, transaction isolation levels, and consistency requirements;
• Define data volume profiles, hot query patterns, pagination strategies, retention policies, and archival needs;
• Document credential sources, TLS configurations, tenant boundaries, row-level permissions, and audit requirements;
• Clarify whether deployments allow downtime, double writes, backfills, or destructive DDL operations.

When real database access is unavailable, distinguish between "code/offline metadata validation" and "real dialect validation." Do not conflate these two approaches in reporting.

Workflow