data-access-guidelines

Type-safe Prisma schemas enforce UUID primary keys with `@id @default(uuid()) @db.Uuid`, standardized timestamp fields, and soft-delete columns. This ensures compile-time type safety and prevents query errors across your data layer.

Implement encapsulated Data Access Objects in `src/lib/dao/` that export a clean public API, handle transactions, apply soft-delete filtering, and map database types to application types. Export DAOs via `src/index.ts` for consistent access patterns.

Define role-based access controls in your Prisma schema and migrations, then enforce them through DAO methods that filter queries by user role. Run migrations with `npx prisma migrate dev --name <descriptive_name>` and regenerate types with `npx prisma generate`.

Yes. Standardize migrations by creating descriptive named migrations, applying them through the migration workflow, and enforcing schema requirements—UUID keys, timestamps, soft deletes, relations—consistently across all new and existing models.

Unit tests for DAOs validate type-safe queries, soft-delete filtering, transaction handling, and role-based access controls. Testing catches query errors and access violations before production and ensures DAOs remain consistent as models evolve.

Without soft deletes, you lose audit trails and risk breaking relations when hard-deleting data. This guideline enforces soft-delete columns and DAO filtering to preserve data integrity, maintain referential consistency, and support compliance requirements.