Use IDs to order tags, special objects, and special morphisms#165
Merged
ScriptRaccoon merged 1 commit intomainfrom May 7, 2026
Merged
Use IDs to order tags, special objects, and special morphisms#165ScriptRaccoon merged 1 commit intomainfrom
ScriptRaccoon merged 1 commit intomainfrom
Conversation
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
1 participant
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 is a continuation of #134 where the
positioncolumn has been removed from the category property assignments and instead an autoincrementing ID was used to order them on the website. In this PR, thepositioncolumn is also removed from the other tables:tagsspecial_object_typesspecial_morphism_typesInstead, an autoincrementing ID is used. This makes the code and inserting the data cleaner. I noticed this while working on #164.
ℹ️ This requires a schema change.