The same letters can be a keyword, identifier, string value, comment, or template fragment depending on delimiters and dialect. Review these boundaries after every transformation.
Quoted content has its own rules
A formatter may uppercase SELECT while leaving `'select'` as a string value and preserving a quoted name such as `"select"`, `` `select` ``, or `[select]` under the matching dialect. Comments should remain comments even when they contain semicolons or keywords. SQLClear reports whether comments were visible before and after formatting, but that Boolean is only a review aid; compare the complete text whenever comments carry instructions or context.
Templates are a separate language
Markers such as `{{ value }}`, `${name}`, ORM placeholders, or migration-tool directives may be meaningful to a preprocessor but invalid to a standalone SQL grammar. Do not remove or rewrite them merely to satisfy a formatter. Format a representative rendered statement when safe, use the toolchain’s own SQL support, or isolate only a plain SQL region. SQLClear deliberately does not substitute parameters because values and quoting belong to the caller’s security boundary.
Review before you run or publish
Keep the original beside the formatted copy and compare literals, quoted identifiers, comments, placeholders, operators, statement boundaries, and vendor-specific clauses. Confirm that the selected dialect matches the actual database and that template markers or procedural blocks are supported. Then use the normal database parser, tests, review, permissions, transaction plan, and backup procedure for the intended change. SQLClear only makes text easier to inspect; it does not execute the script or prove that its behavior, performance, permissions, or data effects are acceptable.