Fixed a key dependency error that caused Sequelize to crash on MariaDB #333
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request Template
Description
I discovered Sequelize would crash on MariaDB when
core/db/migrations/20250118235051-change-grading-attendance.jsattempted to delete QuestionInLecture.order. There was a key constraining QuestionInLecture.order and QuestionInLecture.lectureId, that in turn was constrained to a foreign key binding QuestionInLecture.lectureId and Lecture.id. I made the script not delete QuestionInLecture.order until both keys were deleted too.Fixes #332
Additional Information
Testing on a MySQL-based system is needed.
Checklist:
Before you submit your Pull Request, please make sure you have completed the following tasks: