SQL Quick Actions
SQL Quick Actions let you run reusable SQL templates against the text you have selected in the query editor. Select a table identifier first, then press the shortcut you configured in Settings → Shortcuts.
This is different from SQL Snippets, which insert templates at the cursor through completion. Quick Actions generate SQL from the current selection and send it through the normal execution path.
Manage Quick Actions
Open Settings → Shortcuts and scroll to SQL Quick Actions. Each action contains:
| Field | Purpose |
|---|---|
| Label | Name shown in the settings list. |
| Shortcut | Key combination that runs the action. |
| Status | Enables or disables the action without deleting it. |
| SQL Template | SQL executed after ${table} is replaced with the selected text. |
You can add, edit, enable, disable, or delete actions. Changes are saved immediately from the action dialog, or when you click Apply in the settings window.
Shortcuts that include Mod (Cmd on macOS, Ctrl on Windows/Linux) are recommended. They are less likely to interfere with normal typing than bare letter keys such as Shift+U.
Run a Quick Action
- Select a table name or qualified identifier in the SQL editor, for example
ordersorpublic.users. - Press the configured shortcut.
- DBX replaces every
${table}token with the trimmed selection and executes the expanded SQL.
Example template:
SELECT COUNT(*) FROM ${table}With orders selected, DBX runs:
SELECT COUNT(*) FROM ordersIf nothing is selected, the shortcut does not run and normal editor input continues.
Shortcut Conflicts
DBX checks Quick Action shortcuts against:
- Other Quick Actions in your list
- Built-in editor and global shortcuts shown in Settings → Shortcuts
Conflicting bindings are highlighted and block Apply until you resolve them.
Storage, Sync, and Safety
Quick Actions are editor settings stored in the current DBX runtime. On Desktop, Configuration Cloud Sync can synchronize them with your other editor settings. Connection Config Migration only moves database connections and does not include Quick Actions.
A Quick Action only generates SQL; it does not bypass database permissions or DBX production protection. Review the fully expanded statement before running templates that contain writes or DDL, and follow the Production Safety guidance.