From 5da1d4099401ca371246443ea20b5c6f88cae25f Mon Sep 17 00:00:00 2001 From: mfw78 Date: Fri, 10 Apr 2026 08:30:11 +0000 Subject: [PATCH] Use 'scheme' instead of 'prefix' in DATABASE_URL messages Per review feedback, 'scheme' is the more accurate term for the sqlite:// portion of the URL. --- .env.template | 4 ++-- src/db/mod.rs | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/.env.template b/.env.template index 7468e158..a12559ad 100644 --- a/.env.template +++ b/.env.template @@ -50,9 +50,9 @@ ######################### ## Database URL -## When using SQLite, this should use the sqlite:// prefix followed by the path +## When using SQLite, this should use the sqlite:// scheme followed by the path ## to the DB file. It defaults to sqlite://%DATA_FOLDER%/db.sqlite3. -## Bare paths without the sqlite:// prefix are supported for backwards compatibility, +## Bare paths without the sqlite:// scheme are supported for backwards compatibility, ## but only if the database file already exists. # DATABASE_URL=sqlite://data/db.sqlite3 ## When using MySQL, specify an appropriate connection URI. diff --git a/src/db/mod.rs b/src/db/mod.rs index 7b989e44..4aafe995 100644 --- a/src/db/mod.rs +++ b/src/db/mod.rs @@ -291,7 +291,7 @@ impl DbConnType { err!(format!( "`DATABASE_URL` does not match any known database scheme (mysql://, postgresql://, sqlite://) \ and no existing SQLite database was found at '{url}'. \ - If you intend to use SQLite, use an explicit `sqlite://` prefix in your `DATABASE_URL`. \ + If you intend to use SQLite, use an explicit `sqlite://` scheme in your `DATABASE_URL`. \ Otherwise, check your DATABASE_URL for typos or quoting issues." )) }