Known limitations
This is an honest list of what ruprizzle does and does not do. It is a feature, not an apology: knowing the boundaries up front is how you decide whether the tool is right for your project.
Current release (1.5.1)
- Heuristic renames are suggested automatically. Add
@renamedFromto confirm or ignore the prompt; the diff never renames silently. db pushdoes not write migration files and is only for prototyping.- LSP for
schema.ruprizzleis available viaruprizzle-lspand the VS Code extension ineditor/. Syntax highlighting is also available as a TextMate grammar. - Offline query checking (
ruprizzle check) is available using query manifests captured at test time. See ADR-012. Decimalon SQLite is stored as text by the defaultsqlx::Anypath. Thesqlite-rusqlitefeature parses it back from text at decode time, which removes thesqlx::Anytext round-trip but still stores it as text on disk. If you need real decimal math on SQLite, useIntminor units (e.g. cents) or a PostgreSQL backend.- SQLite
Jsonis stored as text, but the JSON1 extension is used forjson_extract,json_type, andjson_set. Thesqlite-rusqlitefeature also decodesJsonwithout thesqlx::Anytext round-trip. JSON containment (@>) is only a partial key-existence approximation because SQLite JSON1 has no containment operator. - Array columns (
T[]) are supported for scalar and enum types. PostgreSQL stores them as native arrays; SQLite and MySQL store them as JSON text using the dialect's JSON facilities. Array filter operators (has,has_every,has_some,contains,contained_by,overlaps,is_empty,is_not_empty) are implemented across all three backends. - Rich types through
sqlx::Anyare limited. On SQLite,Uuid,Decimal,DateTime,Date,Time, andJsonround-trip as text. Thesqlite-rusqlitefeature parses them from text at decode time, which is faster but still stores them as text in the database. On Postgres, the defaultpostgres://connection uses the nativesqlx::Postgresdriver and binds rich types directly, sosqlx::Anytext marshalling only applies if you explicitly constructPool::Any(...)or use a non-default URL. Thepostgres-tokio-postgresfeature is available as an additional native driver with its own performance characteristics. See ADR-009. SelectQuery::streamis buffered, not a true cursor. The current implementation buffers the full result set and yields decoded rows. Usingsqlx's.fetch()stream is ~64% slower per row on SQLite, so the buffered design is deliberate. See BenchmarkResults.SelectQuery::stream_unbufferedis available for true streaming. It usessqlx's.fetch()cursor for the SQLx backends and a server-side portal forpostgres-tokio-postgres. To satisfysqlx's lifetime model, the owned SQL string and bind values are leaked for the lifetime of the stream (they are typically small).stream_unbufferedmust not be used inside a transaction, because a transaction holds a single connection and a streaming cursor would prevent any other statement from running on it.- MySQL/MariaDB carries an unpatched advisory in its auth path.
sqlx-mysqlpulls inrsa 0.9.x, which is affected by RUSTSEC-2023-0071 (a Marvin timing side-channel in RSA decryption). No patchedrsarelease exists as of 2026-08-21, so the exception is recorded indeny.tomlrather than fixed. The side-channel is reachable only through MySQL'scaching_sha2_passwordRSA key exchange, which is skipped when the connection uses TLS or a unix socket. Use TLS or a unix socket for MySQL connections. Until a patchedrsaorsqlxships, MySQL/MariaDB is supported and tested but is not marketed as production-grade; Postgres and SQLite carry no such exception.
Release-specific gaps (1.6.0)
- Ruprizzle Studio has token authentication only. Since
1.6every request needs the per-run session token (random, or--token/RUPRIZZLE_STUDIO_TOKEN): the launch URL Studio prints (/studio?token=…) sets it as anHttpOnly,SameSite=Strictcookie, and scripts send it asx-studio-tokenorAuthorization: Bearer. There are no user accounts or roles and no TLS, so off loopback the token crosses the network in cleartext. It binds127.0.0.1by default and refuses--allow-writeson a non-loopback host without--yes-i-know; do not expose it on an untrusted network. Since1.5.2it refuses requests whoseHostis not Studio's own name (DNS rebinding) and mutations without Studio'sOriginand session token (CSRF), so a web page open in the same browser cannot drive it. ScriptedPOSTs fromcurlare refused for the same reason. - The Turso and D1 adapters are unverified against the live hosted services.
ruprizzle-turso(Hrana 2 over HTTP) andruprizzle-d1(Cloudflare REST API) are tested end-to-end against local HTTP fakes, not real Turso/D1 databases. Live smoke tests exist (cargo test -p ruprizzle-turso --test live, likewise forruprizzle-d1, and theedge-liveworkflow) but skip without credentials and have not yet been run against the hosted services. Both send one HTTP request per statement, so neither supports interactive transactions, andstream_rawon each is a streaming interface over a fully buffered response. Turso has no embedded-replica support (that needs the native libSQL library), and D1 has no in-Worker/wasm32binding. - D1 parameters and results are JSON. Binary parameters and non-finite floats
(
NaN,±inf) are refused withD1Error::Unsupported. Integers beyond ±2^53 are rounded by D1's JavaScript runtime before the adapter sees them, in both directions; store 64-bit identifiers as text on D1. - There is no Neon adapter, by design. Neon is ordinary Postgres over TLS;
its connection string goes straight to
ruprizzle::connect. - Studio templates use
askama0.14, not the latest 0.15+/0.16, because those need Rust 1.88 and the workspace MSRV is 1.85.
Deferred / not implemented
- Polymorphic relations.
- Row-level security and multi-tenancy (
@@tenant/@@policyare rejected at validation; they were removed from the LSP so they cannot appear to work). - Vector / pgvector search.
- Support for additional databases (MSSQL).
When to choose something else
- Use sqlx directly if you want hand-written SQL and compile-time checked queries today.
- Use Diesel if you need a mature, stable query builder and are comfortable with its DSL.
- Use SeaORM if you want an active-record style API and do not need schema-first code generation.