database-patterns

Standardize Prisma schema design by enforcing consistent id fields, timestamps, explicit indexes, and cascading deletes across all models. This ensures uniform data-modeling practices and maintainable schemas across multiple services and apps in a monorepo.

Safe Prisma migration strategies involve applying backfills, planning safe upgrade paths, and enforcing design rules before deploying schema changes. This prevents data loss and downtime during database migrations across large monorepo environments.

Add explicit indexes to a Prisma schema when querying on non-id fields or enforcing unique constraints across multiple columns. Explicit indexes optimize query performance and are enforced as a required design rule for all data models.

Configure cascading deletes in Prisma schema by defining explicit referential actions on relation fields. This enforces safe data deletion behaviors across related models and prevents orphaned records in the database.

Yes, the Prisma migration guidance includes backfill best practices and safe upgrade paths. It provides concrete examples for migrating and backfilling existing data rows while maintaining schema consistency across services.

Use standardized query-pattern guidance for Prisma data access to ensure consistency across multiple apps. This includes concrete examples for structuring queries, applying indexes, and maintaining safe data retrieval workflows.