A Prettier plugin for SQL that uses sql-parser-cst and the actual Prettier formatting algorithm.

Try it live!

Like Prettier for JavaScript, this plugin formats SQL expressions differently depending on their length. A short SQL query will be formatted on a single line:

SELECT a, b, c FROM tbl WHERE x > 10;

A longer query, will get each clause printed on a separate line:

SELECT id, client.name, client.priority
FROM client
WHERE client.id IN (12, 18, 121);

An even longer one gets the contents of each clause indented:

SELECT
  client.id,
  client.name AS client_name,
  organization.name AS org_name,
  count(orders.id) AS nr_of_orders
FROM
  client
  LEFT JOIN organization ON client.organization_id = organization.id
  LEFT JOIN orders ON orders.client_id = client.id
WHERE
  client.status = 'active'
  AND client.id IN (28, 214, 457)
  AND orders.status IN ('active', 'pending', 'processing')
GROUP BY client.id
ORDER BY client.name
LIMIT 100;

• Adapt formatting based on expression length.
• Stick to one style and avoid configuration options.
• Format embedded languages (like JSON data and JavaScript programs).
• When unsure, preserve existing syntax.

Currently this plugin preserves most of the syntax elements and concentrates mainly on the layout of whitespace.

See STYLE_GUIDE for overview of the SQL formatting style used.

Install it as any other Prettier plugin:

npm install --save-dev prettier prettier-plugin-sql-cst
# or
pnpm add --save-dev prettier prettier-plugin-sql-cst
# or
yarn add --dev prettier prettier-plugin-sql-cst

Then use it on SQL files through Prettier command line tool or Prettier extension for your editor of choice.

By default the plugin will determine SQL dialect based on file extension:

• .sql or .sqlite - SQLite
• .bigquery - BigQuery

You can override this behavior with a prettier configuration in .prettierrc.json file:

{
  "plugins": ["prettier-plugin-sql-cst"],
  "overrides": [
    {
      "files": ["*.sql"],
      "options": { "parser": "bigquery" }
    }
  ]
}

Or you could also store it inside your package.json:

{
  "prettier": {
    "plugins": ["prettier-plugin-sql-cst"],
    "overrides": [
      {
        "files": ["*.sql"],
        "options": { "parser": "bigquery" }
      }
    ]
  }
}

The plugin provides the following parsers:

• sqlite
• bigquery
• postgresql (experimental! expect crashes)
• mysql (experimental! expect crashes)
• mariadb (experimental! expect crashes)

The standard Prettier options printWidth, tabWidth, useTabs apply. There are also some SQL-specific options:

To use this plugin inside VSCode, install the Prettier VSCode extension.

Follow Prettier VSCode docs to configure it as the default formatter.

You might also need to configure prettier.documentSelectors to enable Prettier for *.sql files.

To see what Prettier is, or is not doing - open the VSCode Output window and select the Prettier dropdown. On format, the window should show your inferredParser. It should reconfirm that by showing "parser": "sqlite" (or whichever perser you have configured inside your prettier config overrides section) and plugins with the path to this package. If you don't see that part, Prettier not using this package.

Support for new SQL dialects depends on these dialects being supported by sql-parser-cst. If you really want to, you can open a new issue for that in the parser repo. But be aware that implementing parser support for new dialects takes a lot of work. As long as the ongoing implementation of PostgreSQL, MySQL and MariaDB is not finished, it's unlikely that work on any other dialect will start.

Use prettier-plugin-embed together with prettier-plugin-sql-cst.

Currently this plugin supports two SQL dialects:

• SQLite - full support.
• BigQuery - full support.

It also has experimental support for the following dialects:

• PostgreSQL
• MySQL
• MariaDB

The main limitation is that the parser does not support full syntax of these dialects. One should expect the parser to crash for syntax that's more specific to these dialects. But as long as the parsing succeeds, the formatting should also succeed. Mainly one can expect the formatting of SELECT, INSERT, UPDATE, DELETE statements to work. But beyond that you should keep your expectations low. You have been warned.

The specifics of the SQL formatting style are still very much subject to change. Though the general principles should be mostly in place by now.