#rocket-framework #web-framework #rocket #pool

rocket_sync_db_pools

Rocket async database pooling support for sync database drivers

5 releases

0.1.0 Nov 17, 2023
0.1.0-rc.4 Nov 2, 2023
0.1.0-rc.3 Mar 24, 2023
0.1.0-rc.2 May 9, 2022
0.1.0-rc.1 Jun 9, 2021

#2360 in Database interfaces

Download history 1520/week @ 2024-12-17 656/week @ 2024-12-24 1119/week @ 2024-12-31 1673/week @ 2025-01-07 2089/week @ 2025-01-14 1554/week @ 2025-01-21 1448/week @ 2025-01-28 2015/week @ 2025-02-04 2010/week @ 2025-02-11 1281/week @ 2025-02-18 1641/week @ 2025-02-25 1361/week @ 2025-03-04 2166/week @ 2025-03-11 1599/week @ 2025-03-18 1929/week @ 2025-03-25 1252/week @ 2025-04-01

7,214 downloads per month
Used in 11 crates (10 directly)

MIT/Apache

1MB
14K SLoC

sync_db_pools ci.svg crates.io docs.svg

This crate provides traits, utilities, and a procedural macro for configuring and accessing database connection pools in Rocket. This implementation is backed by r2d2 and exposes connections through request guards.

Usage

First, enable the feature corresponding to your database type:

[dependencies.rocket_sync_db_pools]
version = "0.1.0"
features = ["diesel_sqlite_pool"]

A full list of supported databases and their associated feature names is available in the crate docs. In whichever configuration source you choose, configure a databases dictionary with a key for each database, here sqlite_logs in a TOML source:

[default.databases]
sqlite_logs = { url = "/path/to/database.sqlite" }

In your application's source code:

#[macro_use] extern crate rocket;

use rocket_sync_db_pools::{database, diesel};

#[database("sqlite_logs")]
struct LogsDbConn(diesel::SqliteConnection);

#[get("/logs/<id>")]
async fn get_logs(conn: LogsDbConn, id: usize) -> Result<Logs> {
    conn.run(|c| Logs::by_id(c, id)).await
}

#[launch]
fn rocket() -> _ {
    rocket::build().attach(LogsDbConn::fairing())
}

See the crate docs for full details.

Dependencies

~15–51MB
~877K SLoC