Regenerates the SQLx offline query cache safely after Rust SQL query changes.
npx skills add https://github.com/windmill-labs/windmill --skill update-sqlx
Please help me install this Agent Skill. Skill: update-sqlx Source: https://github.com/windmill-labs/windmill/tree/main/.agents/skills/update-sqlx Command: npx skills add https://github.com/windmill-labs/windmill --skill update-sqlx
Windmill's CI runs with SQLX_OFFLINE=true, so every sqlx::query! macro needs matching cached data in backend/.sqlx/. Running cargo sqlx prepare naively deletes the entire cache before regenerating it, which silently destroys enterprise-edition query entries and breaks CI whenever compilation fails partway.
Update the SQLx offline cache for my new query by backing up backend/.sqlx with the sqlx-cache script, running cargo sqlx prepare against this worktree's database, and restoring any deleted EE entries.
High-intent search queries and answers about installing and using this skill.
Back up backend/.sqlx first, then run cargo sqlx prepare --workspace with the all_sqlx_features flag against a live database. Afterward restore any EE cache entries deleted by prepare and verify with git diff against origin/main.
CI runs with SQLX_OFFLINE=true, so every sqlx::query! macro needs a matching entry in backend/.sqlx/. The error means you added or edited a query without regenerating the cache, or a test-target query was never compiled during prepare.
prepare empties backend/.sqlx before regenerating and only writes entries for code it actually compiles. Without the private EE feature or with a failed compilation, it silently deletes enterprise query caches, so always back up first and restore missing entries from origin/main.
Run cargo sqlx prepare with --all-targets so test targets compile and their queries get cached. In a CE checkout this aborts partway due to an EE-only import, so back up first, then graft only the new entries onto the restored backup.
No. A removal-only change leaves orphaned cache entries that are cosmetic and never break CI. Instead, manually delete the specific .sqlx/query-*.json files whose normalized query text no longer appears in any .rs file, filtered to the tables your change touched.
That error means DATABASE_URL points at the wrong database, typically another worktree's database that lacks your migrations. Point DATABASE_URL at this worktree's own database so prepare compiles queries against the correct schema.
patrickhaahrVerify SQL queries at compile time in Rust applications using sqlx.
zeroclash-labsRun cargo check, test, clippy, and fmt across a Rust workspace.
openmeterioGenerate SQL migrations for ent framework schema changes on PostgreSQL.
adelabdelgawadImplement compile-time verified SQLx queries with macros and dynamic SQL safety.
