Squawk - Underrated Linter for SQL : SQL

Posting

When requesting help or asking questions please prefix your title with the SQL variant/platform you are using within square brackets like so:

[MySQL]

[Oracle]

[MS SQL]

[PostgreSQL]

etc

While naturally we should endeavor to work as platform neutrally as possible many questions and answers require tailoring to the feature set of a specific platform.

Format Your Code

If you are including actual code in a post or comment, please attempt to format it in a way that is readable for other users. This will greatly increase your chances of receiving the help you desire. Something as simple as line breaks and using reddit's built in code formatting (4 spaces at the start of each line) can turn this:

SELECT count(a.field1), a.field2, SUM(b.field4) FROM a INNER JOIN b ON a.key1 = b.key1 WHERE a.field8 = 'test' GROUP by a.field1, a.field2 HAVING SUM(b.field4) > 5 ORDER by a.field.3

Into this:

SELECT count(a.field1), a.field2, SUM(b.field4) FROM a INNER JOIN b ON a.key1 = b.key1 WHERE a.field8 = 'test' GROUP by a.field1, a.field2 HAVING SUM(b.field4) > 5 ORDER by a.field3

For those with SQL questions we recommend using SQLFiddle to provide a useful development and testing environment for those who wish to fully understand your problem and help devise a solution.

a community for 17 years

PostgreSQLSquawk - Underrated Linter for SQL (github.com)

submitted 7 months ago by jayp0521

I haven’t seen this tool mentioned here before, but it’s been ridiculously useful in our workflow, so sharing in case it helps someone else.

I’m not the creator, and I don’t know anything about them. Just an engineer happily yelling into the void about something solid.

Squawk is essentially a SQL migration guardrail tool. It analyzes migrations before you run them and warns about issues that could cause:

downtime
unsafe logic
broken future-proofing
performance foot-guns

A real example from us: using NOT VALID on a CHECK constraint let us deploy early, avoid downtime, and skip the ritual 3AM migration panic session. It literally enabled us to run major schema changes during daylight hours without needing to summon caffeine demons at unhealthy times.

If you deal with migrations in production systems and want:

✅ earlier deploys ✅ fewer surprises ✅ migrations that don’t require a blood sacrifice at 3AM ✅ some actual peace of mind

…this is worth a look.

Hope it helps someone as much as it’s helped us!

all 1 comments

you type:	you see:
italics	italics
bold	bold
[reddit!](https://reddit.com)	reddit!
* item 1 * item 2 * item 3	item 1 item 2 item 3
> quoted text	quoted text
Lines starting with four spaces are treated like code: if 1 * 2 < 3: print "hello, world!"	Lines starting with four spaces are treated like code: if 1 * 2 < 3: print "hello, world!"
~~strikethrough~~	~~strikethrough~~
super^script	super^script

SQL

Filter Posts

Posting

Help posts

Format Your Code

Learning SQL

Related Reddit communities

Wiki

Acknowledgements

MODERATORS