Paste SQL to see the analysis here.
What is this?
Paste production SQL before running an UPDATE or DELETE to get a plain-English explanation of what it does. SQLMegane describes the target, WHERE conditions, and JOIN behavior, and flags common mistakes such as a missing WHERE clause, an always-true condition, or an outer join canceled by WHERE. No account or installation is required.
For MySQL, PostgreSQL, and SQL Server, the bundled parser builds an AST and provides a structural summary and checks. Oracle, Generic, and statements that cannot be parsed use simpler regular-expression checks; the page clearly marks this mode.
For PL/SQL units such as CREATE OR REPLACE PACKAGE / PROCEDURE / FUNCTION / TRIGGER and DECLARE or BEGIN ... END; /, SQLMegane extracts embedded DML and cursor definitions and checks each statement. Control flow such as loops, branches, and exception handling is not analyzed. Review how often each statement runs and what may be rolled back.
This is a prototype. Even successful parsing cannot validate every semantic detail. No detected danger does not mean the SQL is safe. A person must make the final decision; use the verification SELECT and a staging environment where possible.
Interested in a team version?
We are considering team features such as pull-request checks in CI/CD, custom rules, and shared review history. Share questions and requests in GitHub Discussions. Feedback about why SQLMegane did not fit your workflow is equally useful.
Bug reports, false positives, and missed detections are welcome in GitHub Issues. False-positive reports are especially helpful because noisy warnings quickly reduce trust.
Questions and requests Tell us why it did not fit Report a false positive or missed detection