Switch startup DB upgrades to EF migrations
This commit is contained in:
4
FAQ.md
4
FAQ.md
@@ -26,6 +26,10 @@ Backend state is persisted via EF Core + SQLite.
|
||||
|
||||
To start with a clean backend state, stop the app and remove the corresponding SQLite file.
|
||||
|
||||
## Do I need to run manual DB migrations after updating the app?
|
||||
|
||||
Usually no. Startup now uses EF Core migration-based schema upgrades (`Database.Migrate`) and applies pending migrations automatically.
|
||||
|
||||
## Does the backend read SQLite on every API call?
|
||||
|
||||
No. The backend loads state from SQLite once during startup into in-memory state and serves requests from memory. Successful state mutations are then written back to SQLite.
|
||||
|
||||
Reference in New Issue
Block a user