Proposal
Week 4 provides `bad_schema.sql` and `schema_v2.sql` but the README doesn't clearly explain what students should compare or what the expected differences are.
Add a structured comparison exercise (`comparison_exercise.sql` or markdown) asking students to:
- Identify constraints missing from `bad_schema.sql` that exist in `schema_v2.sql`
- List the functional dependencies violated in the bad schema
- Explain what data anomalies are possible in the bad schema
- Run specific INSERT/UPDATE/DELETE statements that succeed on bad_schema but fail on schema_v2
Why
Students need guided discovery, not just two files to diff. Without explicit tasks, the learning outcome ("detect anomalies and integrity violations") is hard to achieve.
Scope / files impacted
- `course/04_week04_constraints/comparison_exercise.md` (new)
- `course/04_week04_constraints/README.md` (add to run order)
Proposal
Week 4 provides `bad_schema.sql` and `schema_v2.sql` but the README doesn't clearly explain what students should compare or what the expected differences are.
Add a structured comparison exercise (`comparison_exercise.sql` or markdown) asking students to:
Why
Students need guided discovery, not just two files to diff. Without explicit tasks, the learning outcome ("detect anomalies and integrity violations") is hard to achieve.
Scope / files impacted