Use `select p.id,p.`name`,c.label from products p join categories c on c.id=p.category_id where p.active=1 and c.label='Home' -- reviewed` with MySQL, two spaces, and uppercase keywords.
Expected layout
SELECT is followed by three lines for `p.id`, `p.`name``, and `c.label`. FROM, JOIN, ON, WHERE, and the two conditions become readable lines under the MySQL profile. The backtick identifier keeps its spelling, `'Home'` remains a case-sensitive-looking string value rather than a keyword, and `-- reviewed` remains a comment at the end. SQLClear does not infer whether the collation actually treats Home as case-sensitive.
Expected evidence
The evidence identifies MySQL and reports comments present both before and after. Source/output character and line counts come from the exact text areas. This proves only that the simple comment pattern remained visible somewhere in the output; compare the line itself. It does not establish that JOIN cardinality, indexes, active values, categories, permissions, or production data are correct.
Reproduce the exact fixture
Open SQLClear, load the example or paste the complete source exactly as printed, select the named dialect, two spaces, and uppercase keywords, then choose Format SQL. Compare every output line with the expected text before copying or downloading. Change the keyword case once and confirm that string values and quoted names remain unchanged. Clear the page and reload it: no query history should return. The example uses fictional catalog data, is never executed, and creates no request to a database or any other host.