[HnR-Autograder:1] DB migration - #7439
Draft
Elimpizza wants to merge 1 commit into
Draft
Conversation
karenrasmussen
approved these changes
Aug 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This pull request introduces a database schema migration to support tracking the predecessor of each auto grading configuration for assignments. The main change is the addition of a self-referential foreign key to the
assignment_auto_grading_configtable, allowing each configuration to reference its previous version. This enables a linear history of configuration changes without allowing forks.Schema changes to
assignment_auto_grading_config:previous_config_idcolumn toassignment_auto_grading_config, allowing each configuration to reference a predecessor.previous_config_idreferencing theidof the same table, with cascading deletes.previous_config_idto ensure that each configuration can only be the predecessor of at most one other configuration, preventing forks in the configuration history.