ruprizzle-orm 1.0.0 (archived announcement)
This announcement was never accurate and is kept only as a record. The
v1.0.0publish run did not upload anything, so1.0.0was never on crates.io. The first published stable release is1.5.1(2026-09-13) — see What's new in v1.1–v1.5 for what actually shipped. See the FAQ and RELEASES.md for the current state. The rest of this page is left as originally written.
ruprizzle-orm 1.0.0 is out on crates.io. It is a schema-first ORM for
Rust: write a Prisma-style schema.ruprizzle, get typed entities, a
Drizzle-style query builder that shows you its SQL, and automatic migrations
generated by diffing your schema. PostgreSQL, MySQL/MariaDB, and SQLite 3+ are
supported. No query engine binary.
This is a stable release. From 1.0.0 onward the public API is covered by
semantic versioning: it does not change without a major bump. See
Stability for exactly what that covers — including which
dependencies are part of our public API — and Known limitations
for the deliberate boundaries.
What we claim
- Automatic migration diffing from a declarative schema — no other Rust ORM has it.
includewith per-relation filters, in a bounded query count.- Column-token typing that rejects cross-model and wrong-type filters at compile time.
- Identical Rust API across PostgreSQL, MySQL/MariaDB, and SQLite.
.to_sql()on every query.- Native
rusqliteandtokio-postgresbackends behind feature flags. - Advanced SQL builders: CTEs (recursive and non-recursive), set operations,
EXISTS/INsubqueries, conditional filters, nested inserts/updates, explicitJOINs, aggregates,GROUP BY/HAVING, and JSON path operators. - Offline / compile-time query checking with
ruprizzle checkand query manifests. - LSP for
schema.ruprizzleviaruprizzle-lspand the VS Code extension ineditor/.
What we explicitly do not claim
- Feature parity with Prisma or Drizzle on every edge-case (vector search, full-text, PostGIS, and implicit many-to-many join tables are deferred to 1.1+).
- That the 1.0 API will not need a second RC if feedback reveals a real problem.
Every one of those would be checked by someone within a day of the post, and being caught overclaiming would cost more than the attention gained.
Supported in this release
- Grammar-driven
.ruprizzleparser with span-preserving diagnostics. - IR lowering, fingerprinting, and round-trip serialisation.
- PostgreSQL, MySQL/MariaDB, and SQLite 3+ dialects with conformance suites.
- Rust entity and query-builder code generation.
- Runtime CRUD, transactions, savepoints, pagination,
includeloading, prepared statements, buffered and unbuffered streaming, and metrics export. - Advanced query builders: conditional/dynamic filters,
INsets, count/exists, aggregates,GROUP BY/HAVING, CTEs, set operations,EXISTS/INsubqueries, nested inserts/updates, explicitJOINs, and JSON path operators. - 12 migration change classes with
up.sql/down.sqlgeneration, drift detection, squashing, rename detection, and FK-cycle handling. - CLI:
init,generate,generate --watch,validate,format,migrate dev,migrate deploy,migrate status,migrate resolve,migrate reset,migrate squash,db push,db pull, anddb seed. trybuildcompile-fail tests that enforce the type-safe query API.cargo xtaskhelpers for CI, examples, hardening, and release.sqlite-rusqliteandpostgres-tokio-postgresfeature flags for native driver performance.ruprizzle-lsplanguage server and VS Code extension.ruprizzle checkfor offline query validation against a schema snapshot.
Get it
cargo install ruprizzle-cli # the `ruprizzle` command
cargo add ruprizzle # the runtime crate your app uses
MSRV is Rust 1.85.
Quickstart
mkdir my-app && cd my-app
ruprizzle init --provider postgres
# Edit schema.ruprizzle, then:
ruprizzle migrate dev --name init
cargo add ruprizzle tokio
cargo run
See the quickstart for the full five-minute walkthrough.
Known limitations
See Known limitations for the full list. Highlights:
- Heuristic renames are suggested automatically; use
@renamedFromto confirm. db pushdoes not write migration files and is only for prototyping.DecimalandJsonon SQLite are stored as text; JSON1 path operators and filters work.- Full-text search, PostGIS, soft deletes, polymorphic relations, and implicit many-to-many join tables are deferred to 1.1+.
Feedback
1.0.0-rc.1 was published on 2026-08-21 and 1.0.0 was cut the same day. The
two-week RC feedback window the project had committed to was waived, in
writing and with its reasoning, in Stability:
across seven prereleases there was no known external consumer to provide the
feedback the window exists to collect. What ran instead was the full release gate
matrix — see ProjectPlan/v1/V1StableRelease.md.
That makes your report the first one. If you find an API problem, open an issue on
the GitHub repository.
Under semver the fix ships as 1.1.0 if it is additive and 2.0.0 if it is not;
neither is a reason to sit on a defect.
One consequence worth knowing before you upgrade: the 1.0 line is pinned to
sqlx 0.8, because ruprizzle re-exports sqlx and the two must be the same
crate. sqlx 0.9 is a 2.0.0 change. Stability.md's "Public dependencies"
section has the details.