rustango 0.34.0

Django-shaped batteries-included web framework for Rust: ORM + migrations + auto-admin + multi-tenancy + audit log + auth (sessions, JWT, OAuth2/OIDC, HMAC) + APIs (ViewSet, OpenAPI auto-derive, JSON:API) + jobs (in-mem + Postgres) + email + media (S3 / R2 / B2 / MinIO + presigned uploads + collections + tags) + production middleware (CSRF, CSP, rate-limiting, compression, idempotency, etc.).
Documentation 
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

//! Migrations for rustango.
//!
//! v0.1 shipped a Postgres DDL writer plus an `apply_all` runner that
//! walks the inventory registry and emits `CREATE TABLE` per
//! `#[derive(Model)]`. Good for bootstrap, no good for evolving schema.
//!
//! v0.2 added **schema snapshots**: capture the registry as JSON, diff
//! against a previous snapshot to produce `CREATE TABLE` / `DROP TABLE`
//! / `ADD COLUMN` / `DROP COLUMN` DDL.
//!
//! v0.3 adds **on-disk migration files** ([`file::Migration`]) that
//! carry both the snapshot and a flat ordered list of schema-or-data
//! operations, plus an apply/rollback runner backed by a
//! `__rustango_migrations__` ledger. The `make_migrations` /
//! `migrate` / `downgrade` UX wraps it all (Slices 2-6).

pub mod ddl;
pub mod diff;
mod error;
pub mod file;
// inspectdb is the migrate CLI's "emit Model derives from a live
// schema" verb. v0.38 — tri-dialect: dispatches per-backend
// (information_schema on PG / MySQL; PRAGMA + sqlite_master on
// SQLite). The module is now reachable on any backend the framework
// supports; the manage CLI runs it via the unified `&Pool` enum.
pub(crate) mod inspectdb;
pub mod invert;
pub mod make;
// v0.35 — the migrate CLI dispatcher (`migrate::manage::run`) is
// v0.38 — `manage::run` now accepts `&crate::sql::Pool` (was &PgPool).
// Each verb routes through the right `_pool` companion in
// `crate::migrate::runner`. The one exception is `inspectdb` which
// queries PG-specific `information_schema` and stays
// `#[cfg(feature = "postgres")]`-gated inside `manage::run_with_writer`.
pub mod manage;
mod runner;
pub mod scaffold;
pub mod snapshot;

pub use diff::{detect_changes, detect_unsupported_field_changes, render_changes, SchemaChange};
pub use error::MigrateError;
pub use file::{discover_migration_dirs, list_dirs, DataOp, Migration, MigrationScope, Operation};
pub use invert::invert;
pub use make::{make_migrations, make_migrations_for_app, make_migrations_from};
#[cfg(feature = "postgres")]
pub use manage::{append_data_op, make_data_migration};
// Always-on: tri-dialect entry points (work on PG / MySQL / SQLite via
// the `Pool` enum), plus the inventory + builder surface.
pub use runner::{
    applied_set_pool, apply_all_pool, downgrade_pool, drop_all_pool, ensure_ledger_pool,
    migrate_dry_run_pool, migrate_embedded_pool, migrate_pool, migrate_to_pool, registered_models,
    unapply_force_pool, unapply_pool, Builder, MigrationPreview, LEDGER_TABLE,
};
// PG-typed back-compat: only re-exported when the `postgres` feature
// is on. Sqlite/MySQL apps use the `_pool` variants above.
#[cfg(feature = "postgres")]
pub use runner::{
    applied_set, apply_all, downgrade, drop_all, ensure_ledger, migrate, migrate_dry_run,
    migrate_embedded, migrate_to, unapply, unapply_force,
};
pub use snapshot::{FieldSnapshot, IndexSnapshot, RelationSnapshot, SchemaSnapshot, TableSnapshot};