Cutlery/jellyfin
1
0
Fork 0
mirror of https://github.com/jellyfin/jellyfin.git synced 2025-06-16 03:54:49 -04:00
Code Issues Packages Projects Releases Wiki Activity

Fixed readme

Browse Source
This commit is contained in:
JPVenson 2025-03-24 10:15:28 +00:00
parent 8e9b57aea9
commit 8d49a396e8
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
src/Jellyfin.Database/readme.md
View File

@ -2,7 +2,7 @@
This shall provide context on how to work with entity frameworks multi provider migration feature.
Jellyfin will support multiple database providers in the future, namely SqLite as its default and the experimental postgresSQL.
Jellyfin will support multiple database providers in the future, namely SQLite as its default and the experimental postgresSQL.
Each provider has its own set of migrations, as they contain provider specific instructions to migrate the specific changes to their respective systems.
@ -12,7 +12,7 @@ When creating a new migration, you always have to create migrations for all prov
dotnet ef migrations add MIGRATION_NAME --project "PATH_TO_PROJECT" -- --provider PROVIDER_KEY
```
with sqlite currently being the only supported provider, you need to run the Entity Framework tool with the correct project to tell EFCore where to store the migrations and the correct provider key to tell jellyfin to load that provider.
with SQLite currently being the only supported provider, you need to run the Entity Framework tool with the correct project to tell EFCore where to store the migrations and the correct provider key to tell Jellyfin to load that provider.
The example is made from the root folder of the project e.g for codespaces `/workspaces/jellyfin`