EF Core Migration - Metadata I18N Support #1338

Open
opened 2025-12-21 18:33:06 +01:00 by backuprepo · 4 comments
Owner

Originally created by @mark-monteiro on GitHub (Mar 5, 2020).

Implement storage of multiple languages for metadata (including images). This would allow admins to define server wide fetch languages allowing for better internationalization support. The admin could say they want 3 languages and then users can decide which order they want these languages to be when displaying metadata.

Originally created by @mark-monteiro on GitHub (Mar 5, 2020). Implement storage of multiple languages for metadata (including images). This would allow admins to define server wide fetch languages allowing for better internationalization support. The admin could say they want 3 languages and then users can decide which order they want these languages to be when displaying metadata.
backuprepo added the
feature
label 2025-12-21 18:33:06 +01:00
Author
Owner

@Wortex17 commented on GitHub (Mar 26, 2023):

Was thinking about doing this since I began using jellyfin, juts found the ticket but I have little information about the whole context of the "entity framework" project.
Is this still going on somewhere?
Don't want to fork/PR on my own Design this if there already is a plan on how to proceed

@Wortex17 commented on GitHub (Mar 26, 2023): Was thinking about doing this since I began using jellyfin, juts found the ticket but I have little information about the whole context of the "entity framework" project. Is this still going on somewhere? Don't want to fork/PR on my own Design this if there already is a plan on how to proceed
Author
Owner

@crobibero commented on GitHub (Mar 26, 2023):

Currently there are a lot of moving parts and other required database changes before this can really even be considered.. so I wouldn't recommend working on this feature yet.

@crobibero commented on GitHub (Mar 26, 2023): Currently there are a lot of moving parts and other required database changes before this can really even be considered.. so I wouldn't recommend working on this feature yet.
Author
Owner

@gentoorax commented on GitHub (Jul 17, 2023):

Many are interested in this feature because it should allow concurrent database access which will eventually allow scalability for those of us using kubernetes. No one seems to have updated issue #42, #987 with a backlink to this which is noted a dependency, to allow those to monitor progress. Interestingly enough I believe plex uses sqlite and still manages to scale in k8s without db locking (not sure how, perhaps sqlite3 readonly features). In any case, many benefits to move to EF including hopefully scalability.

@gentoorax commented on GitHub (Jul 17, 2023): Many are interested in this feature because it should allow concurrent database access which will eventually allow scalability for those of us using kubernetes. No one seems to have updated issue #42, #987 with a backlink to this which is noted a dependency, to allow those to monitor progress. Interestingly enough I believe plex uses sqlite and still manages to scale in k8s without db locking (not sure how, perhaps sqlite3 readonly features). In any case, many benefits to move to EF including hopefully scalability.
Author
Owner

@mark-monteiro commented on GitHub (Jul 17, 2023):

@gentoorax There isn't really any one place where updates can be found for the migration to Entity Framework. It isn't really a single issue that can be tracked as it is a very large task that necessitates an overhaul of large parts of the application. As such, work on it has been slow and has often stalled. As far as I know there hasn't been much to update in a while.

If you want to keep up to date on it, the best place I could find is here: https://features.jellyfin.org/posts/315/mysql-server-back-end

@mark-monteiro commented on GitHub (Jul 17, 2023): @gentoorax There isn't really any one place where updates can be found for the migration to Entity Framework. It isn't really a single issue that can be tracked as it is a very large task that necessitates an overhaul of large parts of the application. As such, work on it has been slow and has often stalled. As far as I know there hasn't been much to update in a while. If you want to keep up to date on it, the best place I could find is here: https://features.jellyfin.org/posts/315/mysql-server-back-end
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: starred/jellyfin#1338
No description provided.