About the SQL formatter
Readable queries for humans
Well-indented SQL is easier to review in migrations, analytics notebooks, and BI exports. Consistent capitalization and line breaks help reviewers spot missing joins, accidental cartesian products, and suspicious literals.
Formatting does not change semantics, but it can reveal mistakes that hide inside minified one-liners copied from generated code.
Dialect differences
SQL is not fully portable. Functions, types, and vendor-specific hints differ between engines. A formatter cannot replace a linter that understands your dialect.
After formatting, run your query through an explain plan on the target database before optimizing indexes or shipping changes.
Collaboration
Agree on basic style rules in your repository so diffs stay small. Pair automated formatting with code review guidelines for naming, comments, and parameterization.
Parameterized queries remain the primary defense against injection; formatting is not a security boundary.