Catch UPDATE/DELETE without WHERE before it runs
How SQLly stops an UPDATE or DELETE with no WHERE clause: editor warnings, a confirmation gate, read-only connections, rollback wraps and production locks.
Read the post →Long-form write-ups on how SQLly works and why it works that way: the guardrails, the plumbing, and the small comforts that make a SQL client pleasant to live in. Every claim here is checked against the docs and the changelog, and anything unfinished is labelled as such.
How SQLly stops an UPDATE or DELETE with no WHERE clause: editor warnings, a confirmation gate, read-only connections, rollback wraps and production locks.
Read the post →How SQLly streams a 50-million-row result: batched reads, a back-pressured channel, spill-to-disk past a threshold, and a grid that pages from the file.
Read the post →SQLly directives are plain SQL comments that pivot, chart, format and lay out your results, so the presentation travels with the .sql file.
Read the post →Schema-aware SQL completion in SQLly: JOIN ON clauses from real foreign keys, stable aliases, real column values, and an F2 loop that turns misses into tests.
Read the post →