Clause-by-Clause SQL Query Explanation

Asking an AI to explain code is one of its strongest capabilities, but without setting the specific "order" and "depth", responses tend to be inconsistent. This prompt standardizes both.

Setting the Role to an "instructor teaching beginners" sets the ideal depth for the explanation. Asking a "Senior DBA" for the same explanation would immediately dive into query plans and index scans. Specifying the dialect in the Context is critical because syntax varies across dialects—LIMIT exists in MySQL and PostgreSQL while SQL Server uses TOP, and date functions vary widely. This single variable prevents unnecessary or irrelevant syntax corrections.

In the Task paragraph, emphasizing "execution order" is key. SQL is written in one order (SELECT first) but executed in another (FROM first), which is where beginners often get confused. Grounding the explanation in execution order clarifies questions like "Why can't I use column aliases in WHERE clauses?"

In the Format section, the "In short..." sentence provides high-level context first, while the "3-row sample table" helps visualize the concrete end result. Without these, even accurate explanations leave users asking, "So what does the final output actually look like?" The Constraint limiting feedback to "just 1 or 2" prevents the model from generating lengthy, nitpicky style advice. Wrapping the query in """ ensures comments inside the query (-- remove this later) are not misinterpreted as instructions.

While you will get an explanation, it typically skims down the query in written order starting from SELECT, missing key beginner questions like "When is the data actually filtered and grouped?" Because no specific DB is mentioned, irrelevant syntax warnings may also appear.