Show HN: SQL Formatter (opens in new tab)

I'm of the same opinion. I always wonder why SQL formatters do this. Is it because it's easier to diff queries with versioning tools? Because to me it's definitely not for legibility. The example shown here isn't even that bad compared to what I see regularly. We've got quiet a few queries longer than 100 sanely written lines running in BigQuery, sometimes I missclick the "format query" option and it always makes me wonder who the hell enjoys scrolling so much because suddenly the line count increases by an order or magnitude or more and the lines aren't much longer than 20 or so characters.

clickhouse-format does it better:

    SELECT COUNT(*)
    FROM table
    ;

    SELECT *
    FROM table
    WHERE (frozen_rand >= 123) AND (frozen_rand <= 456)
    ORDER BY RAND() ASC
    LIMIT 1000
    ;

It also has the "obfuscate" option that is useful for test reports.

    clickhouse-format --obfuscate

I guess it's newlining on certain key words like AND which is ok if it's a new where condition but unnecessary if it's part of an between clause.

Shall we even discuss the weird SQL injection stuff there, with what looks like Python string formatting? Use bind parameters, people!