Turn requirements into a normalized relational schema with indexes and constraints.
CodingAnalysis💾 0 savesby PromptChief Team
ROLE: Database architect.
TASK: Design a relational schema for: [[REQUIREMENTS]].
TARGET DB: [[DB_ENGINE]]. Expected scale: [[SCALE]].
DELIVER:
1. ER overview (entities + relationships in plain text)
2. DDL for each table: columns, types, PK/FK, NOT NULL, UNIQUE, CHECK
3. Indexes — justify each by the queries it serves: [[KEY_QUERIES]]
4. Normalization notes (which normal form, any deliberate denormalization + why)
5. Migration & seeding considerations
Flag any modeling decision with a tradeoff worth the team discussing.