1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136
//! [](https://github.com/rust-secure-code/safety-dance/) [](https://yasamoka.github.io/db-pool) [](https://crates.io/crates/db-pool)
//!
//! A thread-safe database pool for running database-tied tests in parallel with:
//! - Easy setup
//! - Proper isolation
//! - Automatic creation, reuse, and cleanup
//! - Async support
//!
//! ## Description
//!
//! Rather than simply providing a database connection pool that allows multiple connections to the same database, `db-pool` maintains a pool of separate isolated databases in order to allow running database-tied tests in parallel. It also handles the lifecycles of those databases: whenever you pick a database out of the pool, you can be sure that the database is clean and ready to be used. It ensures that databases are isolated so that no other tests are connected to the database you are using in any one test.
//!
//! ## Motivation
//!
//! When running tests against a database-tied service, such as a web server, a test database is generally used. However, this comes with its own set of difficulties:
//!
//! 1) The database has to be either (a) dropped and re-created or (b) cleaned before every test.
//! 2) Tests have to run serially in order to avoid cross-contamination.
//!
//! This leads to several issues when running tests serially:
//!
//! - Test setup and teardown is now required.
//! - Dropping and creating a database from scratch can be expensive.
//! - Cleaning a database instead of dropping and re-creating one requires careful execution of dialect-specific statements.
//!
//! When switching to parallel execution of tests, even more difficulties arise:
//!
//! - Creating and dropping a database for each test can be expensive.
//! - Sharing temporary databases across tests requires:
//! - isolating databases in concurrent use
//! - cleaning each database before reuse by a subsequent test
//! - restricting user privileges to prevent schema modification by rogue tests
//! - dropping temporary databases before or after a test run to reduce clutter
//!
//! `db-pool` takes care of all of these concerns while supporting multiple database types, backends, and connection pools.
//!
//! ### Databases
//!
//! - MySQL (MariaDB)
//! - PostgreSQL
//!
//! ## Backends & Pools
//!
//! ### Sync
//!
//! | Backend | Pool | Feature |
//! | ----------------------------------------------------- | ----------------------------------------- | ----------------- |
//! | [diesel/mysql](struct@sync::DieselMySQLBackend) | [r2d2](https://docs.rs/r2d2/0.8.10/r2d2/) | `diesel-mysql` |
//! | [diesel/postgres](struct@sync::DieselPostgresBackend) | [r2d2](https://docs.rs/r2d2/0.8.10/r2d2/) | `diesel-postgres` |
//! | [mysql](struct@sync::MySQLBackend) | [r2d2](https://docs.rs/r2d2/0.8.10/r2d2/) | `mysql` |
//! | [postgres](struct@sync::PostgresBackend) | [r2d2](https://docs.rs/r2d2/0.8.10/r2d2/) | `postgres` |
//!
//! ### Async
//!
//! | Backend | Pool | Features |
//! | ----------------------------------------------------------------- | ----------------------------------------------------------------------------------------- | ------------------------------------------- |
//! | [diesel-async/mysql](struct@async::DieselAsyncMySQLBackend) | [bb8](https://docs.rs/diesel-async/0.4.1/diesel_async/pooled_connection/bb8/index.html) | `diesel-async-mysql`, `diesel-async-bb8` |
//! | [diesel-async/mysql](struct@async::DieselAsyncMySQLBackend) | [mobc](https://docs.rs/diesel-async/0.4.1/diesel_async/pooled_connection/mobc/index.html) | `diesel-async-mysql`, `diesel-async-mobc` |
//! | [diesel-async/postgres](struct@async::DieselAsyncPostgresBackend) | [bb8](https://docs.rs/diesel-async/0.4.1/diesel_async/pooled_connection/bb8/index.html) | `diesel-async-postgres`, `diesel-async-bb8` |
//! | [diesel-async/postgres](struct@async::DieselAsyncPostgresBackend) | [mobc](https://docs.rs/diesel-async/0.4.1/diesel_async/pooled_connection/mobc/index.html) | `diesel-async-postgres`, `diesel-async-bb8` |
//! | [sea-orm/sqlx-mysql](struct@async::SeaORMMySQLBackend) | [sqlx](https://docs.rs/sqlx/0.7.4/sqlx/struct.Pool.html) | `sea-orm-mysql` |
//! | [sea-orm/sqlx-postgres](struct@async::SeaORMPostgresBackend) | [sqlx](https://docs.rs/sqlx/0.7.4/sqlx/struct.Pool.html) | `sea-orm-postgres` |
//! | [sqlx/mysql](struct@async::SqlxMySQLBackend) | [sqlx](https://docs.rs/sqlx/0.7.4/sqlx/struct.Pool.html) | `sqlx-mysql` |
//! | [sqlx/postgres](struct@async::SqlxPostgresBackend) | [sqlx](https://docs.rs/sqlx/0.7.4/sqlx/struct.Pool.html) | `sqlx-postgres` |
//! | [tokio-postgres](struct@async::TokioPostgresBackend) | [bb8](https://docs.rs/bb8-postgres/0.8.1/bb8_postgres/) | `tokio-postgres`, `tokio-postgres-bb8` |
//! | [tokio-postgres](struct@async::TokioPostgresBackend) | [mobc](https://docs.rs/mobc-postgres/0.8.0/mobc_postgres/) | `tokio-postgres`, `tokio-postgres-mobc` |
#![doc(
html_favicon_url = "https://raw.githubusercontent.com/yasamoka/db-pool/main/logo.svg",
html_logo_url = "https://raw.githubusercontent.com/yasamoka/db-pool/main/logo.svg",
issue_tracker_base_url = "https://github.com/yasamoka/db-pool/issues"
)]
#![forbid(unsafe_code)]
#![deny(
missing_docs,
clippy::cargo,
clippy::complexity,
clippy::correctness,
clippy::pedantic,
clippy::perf,
clippy::style,
clippy::suspicious,
clippy::unwrap_used
)]
#![allow(
clippy::module_name_repetitions,
clippy::module_inception,
clippy::missing_errors_doc
)]
mod common;
/// Async backends
#[cfg(feature = "_async")]
pub mod r#async;
/// Sync backends
#[cfg(feature = "_sync")]
pub mod sync;
mod util;
#[allow(unused_imports)]
pub use common::config::*;
#[cfg(test)]
mod tests {
#![allow(clippy::unwrap_used)]
use std::sync::OnceLock;
use dotenvy::dotenv;
use tokio::sync::RwLock;
use crate::common::config::{mysql::PrivilegedMySQLConfig, postgres::PrivilegedPostgresConfig};
#[cfg(feature = "_mysql")]
pub static MYSQL_DROP_LOCK: RwLock<()> = RwLock::const_new(());
#[cfg(feature = "_postgres")]
pub static PG_DROP_LOCK: RwLock<()> = RwLock::const_new(());
pub fn get_privileged_mysql_config() -> &'static PrivilegedMySQLConfig {
static CONFIG: OnceLock<PrivilegedMySQLConfig> = OnceLock::new();
CONFIG.get_or_init(|| {
dotenv().ok();
PrivilegedMySQLConfig::from_env().unwrap()
})
}
pub fn get_privileged_postgres_config() -> &'static PrivilegedPostgresConfig {
static CONFIG: OnceLock<PrivilegedPostgresConfig> = OnceLock::new();
CONFIG.get_or_init(|| {
dotenv().ok();
PrivilegedPostgresConfig::from_env().unwrap()
})
}
}