IntelliSense
functionalCompletions that pay attention to your query, schema, and, when useful, the data itself.
Good completion should feel like a quiet assist, not a slot machine. SQLly builds suggestions from one SQL model engine: a shared view of your schema and data, rather than a pile of disconnected regexes. It can therefore see where the cursor is in the statement and offer the things that belong there.
- Scope-aware
- SQLly can tell whether you are in a
FROM,WHERE,JOIN ... ON, orEXECparameter list, and adjusts accordingly. - Schema-qualified
- Two-part and schema-qualified names complete cleanly, including the system catalogs SQLly discovers.
- Procedure-aware
EXECparameters and stored-procedure filtering use the same model, with value metadata when it is available.- Careful auto-triggering
- Suggestions appear when they help and stay quiet when they do not; the trigger matcher is checked against regressions.


What it offers where
| Caret position | What the list offers |
|---|---|
SELECT * f▮ (no FROM yet) | FROM first, then tables and views marked adds FROM. Accepting one writes the FROM clause with the name on its own indented line. |
After FROM or JOIN | Schemas, tables, views, functions, and keywords. After JOIN, also ready-made foreign-key joins. |
After JOIN table AS alias, or after ON | Only that table's join conditions built from its foreign keys to earlier tables. |
On a new line after a FROM table | WHERE first, then the query's columns marked adds WHERE. |
WHERE, GROUP BY, ORDER BY, HAVING | Only the columns in scope, functions, parameters, and keywords. Tables and procedures are left out because they cannot appear there. In GROUP BY, the columns the select list still needs come first. |
alias. or schema. | That table's columns, or that schema's tables and views. |
DATEADD(▮ and similar | The fixed words that argument takes, such as year, month, and day, first. |
After @@ | Only the connection's system functions and variables. |
After SET | Only the options your engine can set. If you type a different engine's form, such as PRAGMA on SQL Server, it points you to the right one. |
Matching what you type
Two switches in Settings › Editor › IntelliSense control how your typing matches names. Both are on by default.
- Match camel humps and initials.
SoTaorSTfindsSomeTable, andPoOrranksPurchaseOrderabovePoor. When it is off, suggestions match any part of the name and ignore case. - Include schema name in searching.
dbomfindsdbo.Make. When it is off, only the object's own name is searched unless you type the schema and a dot.
The same pane holds the alias settings.
In the popup, the letters you typed are marked in each suggestion with bold, dark text on a bright highlighter-yellow fill, in every theme, so you can see at a glance why a name matched.
Ranking and inserting
- A name you type in full outranks a fuzzy match on a similar one.
- Items you accept get a boost for the rest of the session, so your usual choices rise.
- Tables related by a foreign key to one already in the query are labeled related via FK and moved up.
- Accepting a suggestion inserts it laid out the way Format SQL would lay out that statement with your formatting settings. See Completions follow your settings.
- Names are quoted only when your engine needs it. A name with a space or a reserved word comes out as
dbo.[Order Details]ordbo.[order]on SQL Server,shop.`Order Details`on MySQL, andpublic."Order Details"on PostgreSQL.
Keys
| Key | Does |
|---|---|
| Ctrl+Space | Opens the list on demand, even where it would not pop up by itself. |
| Ctrl+Shift+Space | Looks up real values for the column you are comparing. See table values. |
| F2 | Reports a bad or missing suggestion while the list is open. See the improvement process. |
These are the defaults on macOS, Windows, and Linux. Cmd+Space is left alone on macOS because Spotlight uses it. Rebind any of them in keybindings.
The two ideas below (schema awareness and data awareness) are what let completion work from the database in front of you rather than a generic SQL dictionary. The same model keeps reading after the query runs: column provenance is how a result column knows which table and column it came from.
In this section
- Schema3 topics
- Suggestions grounded in the tables, columns, routines, and relationships you actually have.
- Data awareness2 topics
- When a column's values matter, SQLly can use them to make the next suggestion more useful.
- Natural-language dates
- Type last wed at 3, november or ytd after a date comparison and SQLly writes the exact literal or range, and keeps it current.
- Column provenance
- SQLly remembers which table and column each result column really came from, so tools can act on the source instead of the label.