Skip to main content
Settings > Editor covers typing and how SQL is displayed. Grid, pagination, result cap and JSON viewer settings are on the Data tab instead. The font here is set per Mac, not per theme, and is not synced.
Editor settingsEditor settings

Editor settings

Font

The picker lists the monospaced families installed on your Mac, at 10 to 24 pt. Cmd+= and Cmd+- change the size over the same range, except while a diagram or a data grid has focus.

Display

Gutter

Editing

Autocomplete is always on; see Autocomplete. Editor shortcuts are listed and customized on Keyboard Shortcuts.

Formatter

Query > Format Query (Cmd+Shift+L) follows these rules. The preview at the end of the section formats a sample statement with them, in the editor theme. The defaults produce the layout shown under Formatting.
Formatter section of Settings Editor with its pickers above a preview of a formatted SELECT statementFormatter section of Settings Editor with its pickers above a preview of a formatted SELECT statement

Each change shows in the preview at once

Restore Defaults puts every formatter setting back.

Share the rules

Click Export… to save the rules as sql-formatter.json. The file holds the resolved values: a width that follows Tab width is written as the number, and Same as editor as the case it means, so the file formats the same on every Mac. Click Import… on another Mac to load it into Settings. To apply the rules to a linked SQL folder instead, save the file in that folder as .sql-formatter.json. A file opened from the folder then formats with it rather than with Settings. The nearest .sql-formatter.json wins, from the file’s own folder up to the linked folder; nothing above the linked folder is read. A rules file that cannot be read stops Format Query with an error naming it. The npm sql-formatter package reads the same file, so one .sql-formatter.json drives both tools.
A key the file leaves out takes the default shown in the example, not your Settings value. For keywordCase that is upper, where sql-formatter keeps the case as written. A key only sql-formatter has, such as language or expressionWidth, is ignored. indentStyle takes sql-formatter’s values, standard, tabularLeft and tabularRight, and changes nothing here. Any value TablePro cannot read is an error that names its key.

A rules file from TablePro 0.83

A file exported by 0.83 uses older key names. Format Query and Import… refuse it with “The value of “indentStyle” is not valid.” Export it again from Settings, or rename the keys: The other keys keep their names.