letro/letro-authentication-service
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 1 Wiki Activity

Fix typos

Browse Source 
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
This commit is contained in:
Quentin Gliech
2025-12-04 16:32:13 +01:00
committed by GitHub
parent 6c5bba19f9
commit cca2015920
2 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
crates/storage-pg/src/lib.rs
View File

@@ -324,7 +324,7 @@ async fn migration_table_exists(conn: &mut PgConnection) -> Result<bool, sqlx::E
/// This function returns an error if the migration fails. /// This function returns an error if the migration fails.
#[::tracing::instrument(name = "db.migrate", skip_all, err)] #[::tracing::instrument(name = "db.migrate", skip_all, err)]
pub async fn migrate(conn: &mut PgConnection) -> Result<(), MigrateError> { pub async fn migrate(conn: &mut PgConnection) -> Result<(), MigrateError> {
// Get the database name and use it to derivate an advisory lock key. This // Get the database name and use it to derive an advisory lock key. This
// is the same lock key used by SQLx default migrator, so that it works even // is the same lock key used by SQLx default migrator, so that it works even
// with older versions of MAS, and when running through `cargo sqlx migrate run` // with older versions of MAS, and when running through `cargo sqlx migrate run`
let database_name = sqlx::query_scalar!(r#"SELECT current_database() as "current_database!""#) let database_name = sqlx::query_scalar!(r#"SELECT current_database() as "current_database!""#)

2
docs/development/database.md
View File

@@ -53,7 +53,7 @@ Note that migrations are embedded in the final binary and can be run from the se
### Removing migrations ### Removing migrations
For various reason, we may want to delete migrations. For various reasons, we may want to delete migrations.
In case we do, we *must* declare that migration version as it is fine to be missing. In case we do, we *must* declare that migration version as it is fine to be missing.
This is because on startup, MAS will validate that all the applied migrations are known, and warn if some are missing. This is because on startup, MAS will validate that all the applied migrations are known, and warn if some are missing.