sql should never be literal strings but instead use a proper abstraction #1
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
bring in a proper orm and proper migration library instead of using literal sql strings, as that is too fragile and too prone to sql injection. There must not be literal SQL in the app, unless it is an absolute necessity due to limitations of the used abstraction layer.
gap: sql should never be literal strings but instead use a proper abstractionto sql should never be literal strings but instead use a proper abstractionImplemented in
ca5eb4e. Replaced application-level literal SQL and rusqlite/refinery with Diesel typed queries, generated schema, and embedded Diesel migrations. Raw SQL is limited to SQLite-specific FTS5, connection PRAGMAs/savepoints, and migration files; an ORM boundary test enforces this. Verified with cargo test --workspace -- --test-threads=1, cargo clippy --workspace --all-targets -- -D warnings, cargo fmt, Diesel migration redo/schema regeneration, and allium check specs/schema.allium.