sql-middleware
Sql-middleware is a lightweight async wrapper for tokio-postgres and rusqlite, with deadpool connection pooling, and an async api (via deadpool-sqlite and tokio-postgres). A slim alternative to SQLx; fewer features, but striving toward a consistent api regardless of database backend.
Motivated from trying SQLx, not liking some issue others already noted, and wanting an alternative.
Goals
- Convenience functions for common sql query patterns
- Keep underlying flexibility of deadpool-sqlite and deadpool-postgres.
- Minimal overhead (just syntax convenience/wrapper fns).
Examples
More examples available in the tests dir, and this is in-use with a tiny little website app, rusty-golf.
Importing
Use the prelude to import everything you need, or import stuff item by item:
use sql_middleware::prelude::*;
Get a connection from the pool
Similar api regardless of db backend.
|
PostgreSQL
|
SQLite
|
let mut cfg = deadpool_postgres
::Config::new();
cfg.dbname = Some("test_db"
.to_string());
cfg.host = Some("192.168.2.1"
.to_string());
cfg.port = Some(5432);
cfg.user = Some("test user"
.to_string());
cfg.password = Some("passwd"
.to_string());
let c = ConfigAndPool
::new_postgres(cfg)
.await?;
let conn = MiddlewarePool
::get_connection(&c.pool)
.await?;
|
let cfg =
"file::memory:?cache=shared"
.to_string();
// same api for connection
// sqlite just has fewer required
// config items (no port, etc.)
let c = ConfigAndPool::
new_sqlite(cfg)
.await?;
let conn = MiddlewarePool
::get_connection(&c.pool)
.await?;
|
Batch query w/o params
Same api regardless of db backend.
|
PostgreSQL
|
SQLite
|
// simple api for batch queries
let ddl_query =
include_str!("/path/to/test1.sql");
conn.execute_batch(&ddl_query).await?;
|
// same api
let ddl_query =
include_str!("/path/to/test1.sql");
conn.execute_batch(&ddl_query).await?;
|
Parameterized Queries
Consistent api for running parametrized queries using the QueryAndParams struct. Database-specific parameter syntax is handled by the middleware.
|
PostgreSQL
|
SQLite
|
// Create query with parameters
// tokio-postgres uses $-style params
let q = QueryAndParams::new(
"INSERT INTO test (espn_id, name, ins_ts)
VALUES ($1, $2, $3)",
vec![
RowValues::Int(123456),
RowValues::Text("test name"
.to_string()),
RowValues::Timestamp(
NaiveDateTime::parse_from_str(
"2021-08-06 16:00:00"
, "%Y-%m-%d %H:%M:%S")?,
),
]);
// Convert params using the ParamConverter trait
let converted_params =
convert_sql_params::<PostgresParams>(
&q.params,
ConversionMode::Execute
)?;
// Execute the query
conn.execute_dml(
&q.query,
&converted_params)
.await?;
|
// Create query with parameters
// rusqlite uses ?-style params
let q = QueryAndParams::new(
"INSERT INTO test (espn_id, name, ins_ts)
VALUES (?1, ?2, ?3)",
vec![
RowValues::Int(123456),
RowValues::Text("test name"
.to_string()),
RowValues::Timestamp(
NaiveDateTime::parse_from_str(
"2021-08-06 16:00:00"
, "%Y-%m-%d %H:%M:%S")?,
),
]);
// Similar API for parameter conversion
let converted_params =
convert_sql_params::<SqliteParamsExecute>(
&q.params,
ConversionMode::Execute
)?;
// Execute the query
conn.execute_dml(
&q.query,
&converted_params)
.await?;
|
Queries without parameters
You can create queries without parameters using new_without_params, same whether using sqlite or postgres:
let query = QueryAndParams::new_without_params(
"SELECT * FROM users"
);
let results = conn.execute_select(&query.query, &[]).await?;
Transactions with custom logic
Here, the APIs differ, because the underlying database's transaction approach differs. It doesn't appear easy to make these consistent. But this is the way to do queries if you need custom app logic between connection.transaction() and connection.commit().
|
PostgreSQL
|
SQLite
|
// Get PostgreSQL-specific connection
let pg_conn = match &conn {
MiddlewarePoolConnection::Postgres(pg)
=> pg,
_ => panic!("Expected Postgres connection"),
};
// Get client
let pg_client = &pg_conn.client;
let tx = pg_client.transaction().await?;
// could run custom logic anywhere between stmts
// Prepare statement
let stmt = tx.prepare(&q.query).await?;
// Convert parameters
let converted_params =
convert_sql_params::<PostgresParams>(
&q.params,
ConversionMode::Execute
)?;
// Execute query
let rows = tx.execute(
&stmt,
converted_params.as_refs()
).await?;
tx.commit().await?;
|
// Get SQLite-specific connection
let sqlite_conn = match &conn {
MiddlewarePoolConnection::Sqlite(sqlite)
=> sqlite,
_ => panic!("Expected SQLite connection"),
};
// Use interact for async tx
let rows = sqlite_conn
.interact(move |conn| {
let tx = conn.transaction()?;
// Convert parameters
let converted_params =
convert_sql_params::<SqliteParamsExecute>(
&q.params,
ConversionMode::Execute
)?;
// could run custom logic anywhere between stmts
// Create parameter references
let param_refs: Vec<&dyn ToSql> =
converted_params.0.iter()
.map(|v| v as &dyn ToSql)
.collect();
// Prepare and execute
let rows = {
let mut stmt = tx.prepare(&q.query)?;
stmt.execute(¶m_refs[..])?
};
tx.commit()?;
Ok::<_, SqlMiddlewareDbError>(rows)
})
.await?;
|
Using the AsyncDatabaseExecutor trait
The AsyncDatabaseExecutor trait provides a consistent interface for database operations:
// This works for both PostgreSQL and SQLite connections
async fn insert_user<T: AsyncDatabaseExecutor>(
conn: &T,
user_id: i32,
name: &str
) -> Result<(), SqlMiddlewareDbError> {
let query = QueryAndParams::new(
// Use appropriate parameter syntax for your DB
// if you don't, it will probably fail
"INSERT INTO users (id, name) VALUES ($1, $2)",
vec![
RowValues::Int(user_id),
RowValues::Text(name.to_string()),
]
);
// Execute query through the trait
conn.execute_dml(
&query.query,
&conn.convert_params(&query.params, ConversionMode::Execute)?
).await?;
Ok(())
}