From 8d49a396e8f68b3940d82b0018f882a37df245d9 Mon Sep 17 00:00:00 2001 From: JPVenson Date: Mon, 24 Mar 2025 10:15:28 +0000 Subject: [PATCH] Fixed readme --- src/Jellyfin.Database/readme.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/Jellyfin.Database/readme.md b/src/Jellyfin.Database/readme.md index 344ba2f4d1..c2d2282b2f 100644 --- a/src/Jellyfin.Database/readme.md +++ b/src/Jellyfin.Database/readme.md @@ -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`