Conversation
CyanVoxel
added
Priority: Critical
Computerdores
approved these changes
Jul 4, 2026
Computerdores
approved these changes
Jul 4, 2026
github-project-automation
Bot
moved this from 🍃 Pending Merge
to ✅ Done
in TagStudio Development
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
2 participants
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.
Summary
This PR applies a migration patch similar to 102 that fixes existing library data where a child tag that is referenced in a
tag_parentsrelationship has been deleted but the relationship has remained in the database. This should be enough to fix #1419. Bumps the DB version to 202.Since the
parent_idside of deletingtag_parentrelationships was corrected in #1107, it shouldn't be necessary to correct for invalid data in this direction as migration 102 did. Meanwhile #1250 ensures that no invalid data like this should be left behind going forward.Tasks Completed