How to use QueryPlan
Start with the task and source tables. Use returned rows to check meaning, then inspect the plan when the exercise asks about database work.
On this page
Run and Submit
Select Run to execute your query on the lesson's sample data and add an entry to Run history. Use the returned rows and plan to inspect your query while you work. Run does not mark the exercise complete.
Select Submit to check your query against the lesson's required results and any plan requirements across all test datasets. The preview shows the original sample data. A query that works on the sample can still fail another checked case.
Read the evidence
The Results tab shows the columns and rows your query returned. The Query plan tab shows how SQLite reads the data. Submission checks report results and plan requirements separately, so a query with correct rows can still need a different plan.
Plan requirements depend on the task. When an exercise has no plan requirements, a SCAN can be valid if the results pass. When it asks for an index search or avoiding a sort, inspect the plan checks as well as the rows.
Hints and reset
Hints provide one step at a time. Read a hint and revise your SQL, then run the query again. Reloading the lesson restores the starter query and discards your current editor text. Copy any SQL you want to keep before reloading.
On the homepage, Reset example returns the small index lesson to its starting state.
The public challenge
The homepage's index challenge lets you try an assessed query and read separate result and plan feedback. It does not advance course progress. Start the free Module 1 exercises.
Local SQL and saved progress
Your schema and SQL run in the browser. Copy any editor text you want to keep, because the course does not save it as a notebook. Foundations progress stays in the current browser. Performance course progress is saved locally and syncs to your account when you are signed in. Wait for a pending save to finish before leaving.
The visualizer is a separate workspace for exploring schema, queries, and plans. Open the free visualizer.
When something goes wrong
For a SQL error, check the table and column names against the schema, then run a smaller query. For failed submission checks, read the result or plan message before changing the query.
For an account, saved-progress, or course-access problem, include what you were trying to do and the page you were using. Contact support.