backend-models-standards

Define database models with clear naming, constraints, and relationships. Enforce data integrity at both model and database levels.

• Models define data structure, not business logic
• Use explicit primary keys and timestamps for data lineage
• Enforce data integrity with database constraints and application validation
• Maintain normalization by default, denormalize only for performance

• Timestamps (created_at, updated_at) on every model
• Primary keys must be explicit (UUID or auto-increment)
• Use database constraints (NOT NULL, UNIQUE, CHECK) for data integrity
• Index queried columns and foreign keys for performance
• Define both sides of relationships with explicit cascade behavior
• Validate data at both model and database levels
• Avoid business logic in models; keep it in service layer
• Use appropriate data types (DECIMAL, VARCHAR, BOOLEAN, etc.)

1. 1.Create or modify model files (models.py, Prisma schema, etc.)
2. 2.Define table relationships (one-to-many, many-to-many) with explicit back_populates
3. 3.Add timestamps and constraints (NOT NULL, UNIQUE, CHECK)
4. 4.Index frequently queried or joined columns
5. 5.Set cascade behaviors (CASCADE, SET NULL, RESTRICT) based on business rules
6. 6.Separate business logic from model definitions