SQLFix FAQ — natural-language SQL, safety, and dialects answered

Supported dialects

SQLFix supports PostgreSQL, MySQL, SQLite, and BigQuery. You choose the dialect per query, and the output is written to match that engine's syntax. If your engine is not on that list, the query may need manual adjustment.

How the safety ruleset works

After a query is generated, the deterministic ruleset (sql-safety) checks it for injection-prone construction, DROP/TRUNCATE without a guard, and UPDATE/DELETE that affect every row, plus obvious dialect syntax problems. Findings are attached to the query so you can read them. It catches the patterns it knows; it is not a full validator.

The free tier

SQLFix offers a free tier with a limited number of workflow runs per day and a watermarked export. Paid tiers raise the run cap and add an audit log and JSON/CSV export. Pricing is listed on the product page; this article does not quote a number that may change.

When to still use a database reviewer

Anything that writes, deletes, or alters production data should be reviewed by a qualified person before it runs — especially on large or shared tables. SQLFix can help you draft and screen; it does not replace that review, and it does not guarantee the query is safe.

Data you send

The schema and question you paste are used to generate and screen the query. Treat anything you paste as sensitive if it contains real column names or sample values from production, and follow your own data-handling rules.

An honest limit

SQLFix is a drafting and review aid. It can help you write dialect-correct SQL and flag known dangers, but it does not guarantee correctness or safety, and it is not a database administrator.

Authoritative references

PostgreSQL documentation: https://www.postgresql.org/docs/current/
OWASP Top 10 — Injection: https://owasp.org/Top10/A03_2021-Injection/

FAQ

Which SQL dialects does SQLFix support?

SQLFix supports PostgreSQL, MySQL, SQLite, and BigQuery. You select the dialect per query and the output is written to match that engine's syntax.

How does the SQLFix safety ruleset work?

After generation, the deterministic ruleset checks the query for injection-prone construction, DROP/TRUNCATE without a guard, and UPDATE/DELETE that affect every row, plus obvious dialect syntax issues. Findings are attached to the query.

Is there a free tier for SQLFix?

Yes. SQLFix offers a free tier with a limited number of workflow runs per day and a watermarked export. Paid tiers raise the cap and add an audit log and JSON/CSV export; see the product page for current pricing.

Does SQLFix replace a database administrator?

No. SQLFix is a drafting and review aid. Anything that writes, deletes, or alters production data should still be reviewed by a qualified person before it runs.

Should a SQLFix query be run without review?

No. SQLFix can help flag known-dangerous patterns, but it does not guarantee a query is correct, safe, or optimal for your schema. A human should review the result before running it.

## Disclaimer

Disclaimer (decision-support, not a guarantee): SQLFix is a tool that helps you turn a plain-English question into a dialect-aware SQL query with a readable explanation and a deterministic safety screen. It is decision-support, not a guarantee that a query is correct, safe, or optimal, and it is not a replacement for a qualified database reviewer. Always review generated SQL — especially any statement that writes, deletes, or alters data — before running it against a production database.

Try SQLFix — ask in plain English, get a dialect-aware SQL query with the dangerous patterns flagged — try SQLFix.