How to use the SQL Query Explainer.
Explain the query's actual operations and edge cases. Pay attention to join behavior, NULL values and aggregation rather than paraphrasing column names alone.
Make the workflow fit your task.
Follow the query through filtering, joining and aggregation, explaining what one output row represents. Use a small example to clarify NULL handling or duplicate behavior rather than only translating each keyword.
- What you provide
- Query and schema context.
- What you get
- Step-by-step account of joins, filters and output.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
SELECT region, COUNT(*) FROM customers GROUP BY region;
Completed example
Groups rows by region and counts rows in each group; confirm how missing region values should be interpreted.
Load this input into the prompt, then copy it to WebAct to try the task. Your result may differ from the illustration.
Decisions and troubleshooting.
Does COUNT(*) mean the same thing as counting a nullable column?
COUNT(*) counts rows; counting a column counts non-NULL values. Check which meaning the query needs.
Why does a LEFT JOIN explanation miss disappearing rows?
Inspect filters applied after the join. A condition on the joined table can affect unmatched rows and change the apparent outer-join behavior.
Try it with your own source.
Replace the example with your material in the task prompt. Keep the requirements you need, then copy the task into WebAct.
Customize and copy the task ↑