mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-07-16 05:43:54 +03:00
[PR #12597] [CLOSED] Userdatakey fix #13281
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/jellyfin/jellyfin/pull/12597
Author: @piratefin
Created: 9/6/2024
Status: ❌ Closed
Base:
release-10.9.z← Head:userdataskey_fix📝 Commits (2)
97e6fb6Added "tmdb-" prefix to tmdb userdatakeys72ac52cAdded "tvdb-" prefix to tmdb userdatakeys📊 Changes
2 files changed (+3 additions, -3 deletions)
View changed files
📝
MediaBrowser.Controller/Entities/TV/Series.cs(+1 -1)📝
MediaBrowser.Controller/Entities/Video.cs(+2 -2)📄 Description
[DRAFT]
[DRAFT]
[DRAFT]
Currently tmdb and tvdb userdatakeys are added as digits only. This has caused confusion especially when marking favorites.
This fixes the issue by adding a prefix for each case. IMDB userdatakeys already have a "tt" prefix that differentiates them.
I have tested this in a personal instance and it works.
Changes
The column "UserDataKey" in table "TypedBaseItems" of library.db will now have "tvdb-" appended if the userdatakey is derived from the tvdb id, and "tmdb-" appended if derived from a tmdb id.
Issues
Fixes #11840
Problems
This fixes the issue completely going forward. However, the current watch history data in the "key" column in "Userdatas" table will not match. The current data needs to be migrated. Proposed migration method is to:
Unfortunately i dont know to put in a migration script. This would need someone else's help.
Thus, this PR is still in [DRAFT].
Please give any comments.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.