SQLFluff

[Revadike]

This is by far the best SQL formatter I've tried (that works with VSCode). Since Supabase already includes linting suggestions in their documentation and AI prompts, why not release a recommended sqlfluff config which will let us easily auto-format our SQL files!

https://sqlfluff.com/

[encima]

Hey, thanks for opening!
As Supabase is "just Postgres", there is not really any special config that would be needed for SQLFluff, you just need to specify the dialect as postgres

[Revadike]

Hey, thanks for opening! As Supabase is "just Postgres", there is not really any special config that would be needed for SQLFluff, you just need to specify the dialect as postgres

I know it's not needed, it will just be a nice to have. I know supabase mentions some formatting recommendations in the docs. Having the ability to auto-format to follow these would just be convenient.

[GitNimay]

Great suggestion, and SQLFluff is genuinely one of the better SQL linting and formatting tools available right now, especially with its VSCode extension and dialect-aware rules.

A Supabase-recommended .sqlfluff config would be a low-effort, high-value addition given that Supabase already enforces SQL conventions through its linter and AI prompt guidance. Having an official config would close the gap between "here are our conventions" and "here is a file that enforces them automatically."

A starting point for a Supabase-flavored config targeting PostgreSQL might look like this:

[sqlfluff]
dialect = postgres
templater = raw
max_line_length = 120
exclude_rules = RF02

[sqlfluff:indentation]
indent_unit = space
tab_space_size = 4

[sqlfluff:rules:capitalisation.keywords]
capitalisation_policy = upper

[sqlfluff:rules:capitalisation.identifiers]
capitalisation_policy = lower

[sqlfluff:rules:capitalisation.functions]
capitalisation_policy = upper

[sqlfluff:rules:convention.select_trailing_comma]
select_clause_trailing_comma = forbid

This enforces uppercase keywords, lowercase identifiers, and PostgreSQL dialect, which aligns with the style used in most Supabase documentation and generated migration files.

If the team is open to it, a good home for this would be the supabase/supabase repo as a docs page under "Local Development" alongside the existing linting guidance, or even as part of the supabase init scaffold so new projects get the config file automatically.

Would be happy to put together a more complete config and open a PR or discussion in the main repo if that is the preferred path forward.