reliar-store-postgres 0.7.0

PostgreSQL provider for the Reliar transactional outbox and inbox: migrations, migrate(), enqueue and the SKIP LOCKED claim.
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22

//! [`PostgresOutboxStore`]: construction, `enqueue`, and the `OutboxStore`/`OutboxEnqueue`/
//! `OutboxDeadLetters` implementations, split by concern — `outbox_store` (the type,
//! construction, shared helpers, plus the `OutboxStore` trait impl itself), `error`
//! ([`PostgresOutboxError`]/[`EnqueueError`]), `enqueue` (the whole `OutboxEnqueue` impl), `claim`
//! (`acquire`'s body), `outcomes` (`complete`/`fail`/`release`/`extend_lease`'s bodies), `purge`
//! (`purge`/`stats`'s bodies), `dead_letters` (the whole `OutboxDeadLetters` impl). Only
//! `OutboxStore` follows the "impl in `outbox_store.rs`, body per method in its concern module"
//! shape, so a reader who wants "what does `acquire` return" starts there regardless of where the
//! body lives; `OutboxEnqueue` (`enqueue.rs`) and `OutboxDeadLetters` (`dead_letters.rs`) are
//! small enough that their whole impl — signature and body — lives in one concern module instead.
//! `enqueue.rs` has no `crate::inbox` counterpart: the inbox has no caller-transaction write side.

mod claim;
mod dead_letters;
mod enqueue;
mod error;
mod outbox_store;
mod outcomes;
mod purge;

pub use error::{EnqueueError, PostgresOutboxError};
pub use outbox_store::PostgresOutboxStore;