SQL Editor

​

Run your first query

​

Running several statements

• On engines with transactions, the batch runs inside one. A failure stops it and rolls back everything before it. Engines without transactions run each statement as-is, with nothing to roll back.
• The error names its place in the run: “Statement 3/5 failed: …”.
• Each statement gets its own result tab, and each is recorded separately in query history.

​

Statement markers

• The statement holding the cursor gets a faint band behind it. It is a decoration, not a selection, so your next keystroke does not replace it.
• Move the pointer over the gutter and a run button appears beside every statement. Click one to run that statement while the cursor is elsewhere. Their column is reserved at all times, so revealing them never shifts the text.
• A run button takes the same safe mode checks and parameter prompts as any other run, and dims while a query is running.
• VoiceOver reads each button as a button naming the line its statement starts on.
• A BEGIN … END body counts as one statement, so a trigger or stored procedure gets one button rather than one per line inside it. BEGIN; and BEGIN TRANSACTION; are statements of their own.

​

Moving between statements

​

Inline diagnostics

​

Per-tab database picker

​

Find and replace

​

Formatting

select u.id,u.name,count(o.id) as order_count from users u left join orders o on u.id=o.user_id where u.status='active' group by u.id,u.name having count(o.id)>5 order by order_count desc;

SELECT
  u.id,
  u.name,
  COUNT(o.id) AS order_count
FROM users u
LEFT JOIN orders o ON u.id = o.user_id
WHERE u.status = 'active'
GROUP BY u.id, u.name
HAVING COUNT(o.id) > 5
ORDER BY order_count DESC;

​

AI assistance

​

Editor settings