SQL Safety Checker

1 destructive or high-risk statement(s) found (highest: high).

How it works

• Split the script into top-level statements.
• Classified each statement and checked for a WHERE guard where one is required.
• Reported every destructive shape with a severity and a basis.

• Severities are high for DROP/TRUNCATE/DELETE-without-WHERE and medium for UPDATE-without-WHERE/ALTER ... DROP/privilege changes.

Methodology

1. Split the script into top-level statements, respecting strings, identifiers and comments.
2. Classify each statement's leading command and whether it carries a WHERE clause.
3. Assign a severity and a plain-language basis to every destructive or high-risk shape found.

Usage

1. Paste a SQL statement or a migration script.
2. Choose the dialect.
3. Run the checker and review each flagged statement and its basis before acting.

Examples

These are examples, not current values: they use fixed inputs, while the interactive tool computes live results in your browser.

A destructive migration

{
  "text": "DROP TABLE users;",
  "dialect": "postgresql"
}

Delete without a WHERE clause

{
  "text": "DELETE FROM audit_log;",
  "dialect": "mysql"
}

A guarded delete is safe

{
  "text": "DELETE FROM sessions WHERE expires_at < now();",
  "dialect": "postgresql"
}

Limitations

Review before you run

A migration that drops a column or truncates a table cannot be undone by a transaction in every engine. Reading the flagged statements first is the cheapest possible safeguard.

Nothing is executed

The checker is a reader: it tokenises the text in your browser and reports what it sees. It opens no connection and runs no statement.