axum-impl-database

To share a sqlx connection pool safely in Axum, build the PgPool once at startup using PgPoolOptions and pass it via router State<PgPool>, avoiding Arc or Mutex wrapping for direct, safe handler access.

The best way to handle sqlx transactions in Axum is using the transaction method with drop-rollback safety, ensuring atomic operations that automatically roll back if a query fails before commit.

Yes, you need to set acquire_timeout in PgPoolOptions to ensure Axum service reliability under load, preventing requests from hanging indefinitely when the sqlx connection pool becomes saturated.

Yes, the DatabaseConnection FromRequestParts extractor requires version-aware migration or implementation adjustments when moving between Axum 0.7 and 0.8 to maintain correct request extraction behavior.

You should use Result propagation instead of unwrap on sqlx queries in Axum handlers to enforce safe error handling, preventing application panics and allowing proper error responses when query execution fails.

Use sqlx compile-time checked query macros when you want static SQL validation during builds, and use runtime query functions like fetch_one or fetch_all in Axum when you need dynamic SQL query construction.