xiner/CICD
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge exams grading into homework
Some checks failed
CI / build-and-test (push) Failing after 3m34s
Details
CI / deploy (push) Has been skipped
Details

Browse Source 
Redirect /teacher/exams/grading* to /teacher/homework/submissions; remove exam grading UI/actions/data-access; add homework student workflow and update design docs.
This commit is contained in:
SpecialX
2025-12-31 11:59:03 +08:00
parent f8e39f518d
commit 13e91e628d
36 changed files with 4491 additions and 452 deletions
Download Patch File Download Diff File Expand all files Collapse all files

54
docs/db/schema-changelog.md
View File

@@ -1,12 +1,12 @@
# Database Schema Changelog
## v1.1.0 - Exam Structure & Performance Optimization
## v1.1.0 - Exam Structure Support
**Date:** 2025-12-29
**Migration ID:** `0001_flawless_texas_twister`
**Author:** Principal Database Architect
### 1. Summary
This release introduces support for hierarchical exam structures (Sectioning/Grouping) and optimizes database constraint naming for better compatibility with MySQL environments.
This release introduces support for hierarchical exam structures (Sectioning/Grouping).
### 2. Changes
@@ -23,17 +23,55 @@ This release introduces support for hierarchical exam structures (Sectioning/Gro
>
```
#### 2.2 Table: `questions_to_knowledge_points`
* **Action**: `RENAME FOREIGN KEY`
### 3. Migration Strategy
* **Up**: Run standard Drizzle migration.
* **Down**: Revert `structure` column. Note that FK names can be kept short as they are implementation details.
### 4. Impact Analysis
* **Performance**: Negligible. JSON parsing is done client-side or at application layer.
* **Data Integrity**: High. Existing data is unaffected. New `structure` field defaults to `NULL`.
## v1.2.0 - Homework Module Tables & FK Name Hardening
**Date:** 2025-12-31
**Migration ID:** `0002_equal_wolfpack`
**Author:** Principal Database Architect
### 1. Summary
This release introduces homework-related tables and hardens foreign key names to avoid exceeding MySQL identifier length limits (MySQL 64-char constraint names).
### 2. Changes
#### 2.1 Tables: Homework Domain
* **Action**: `CREATE TABLE`
* **Tables**:
* `homework_assignments`
* `homework_assignment_questions`
* `homework_assignment_targets`
* `homework_submissions`
* `homework_answers`
* **Reason**: Support assignment lifecycle, targeting, submissions, and per-question grading.
#### 2.2 Foreign Keys: Homework Domain (Name Hardening)
* **Action**: `ADD FOREIGN KEY` (with short constraint names)
* **Details**:
* `homework_assignments`: `hw_asg_exam_fk`, `hw_asg_creator_fk`
* `homework_assignment_questions`: `hw_aq_a_fk`, `hw_aq_q_fk`
* `homework_assignment_targets`: `hw_at_a_fk`, `hw_at_s_fk`
* `homework_submissions`: `hw_sub_a_fk`, `hw_sub_student_fk`
* `homework_answers`: `hw_ans_sub_fk`, `hw_ans_q_fk`
* **Reason**: Default generated FK names can exceed 64 characters in MySQL and fail during migration.
#### 2.3 Table: `questions_to_knowledge_points`
* **Action**: `RENAME FOREIGN KEY` (implemented as drop + add)
* **Details**:
* Old: `questions_to_knowledge_points_question_id_questions_id_fk` -> New: `q_kp_qid_fk`
* Old: `questions_to_knowledge_points_knowledge_point_id_knowledge_points_id_fk` -> New: `q_kp_kpid_fk`
* **Reason**: Previous names exceeded MySQL's 64-character identifier limit, causing potential migration failures in production environments.
### 3. Migration Strategy
* **Up**: Run standard Drizzle migration. The script includes `ALTER TABLE ... DROP FOREIGN KEY` followed by `ADD CONSTRAINT`.
* **Down**: Revert `structure` column. Note that FK names can be kept short as they are implementation details.
* **Up**: Run standard Drizzle migration. The migration is resilient whether the legacy FK names exist or have already been renamed.
* **Down**: Not provided. Removing homework tables and FKs is destructive and should be handled explicitly per environment.
### 4. Impact Analysis
* **Performance**: Negligible. JSON parsing is done client-side or at application layer.
* **Data Integrity**: High. Existing data is unaffected. New `structure` field defaults to `NULL`.
* **Performance**: Minimal. New indexes are scoped to common homework access patterns.
* **Data Integrity**: High. Foreign keys enforce referential integrity for homework workflow.