Mode disclosure
All modes use one coherent workspace; only disclosure and guidance change. Practice mode uses a concise prompt, normal schema, optional hints, and the same local Run and Check pipeline.
Tables, Rows, Columns, Keys, and Grain / predict result
M01-A01 - Schema reasoning - match three tiny tables to row-grain statements
M01-A01 - Schema reasoning - match three tiny tables to row-grain statements. State row grain, distinguish identifiers from labels, and preview relationships.
- Result grain
- one row per matched table
- Exact columns
- table_name; row_grain
SQL editor shortcuts: Ctrl or Command Enter runs the query, Ctrl or Command Shift Enter checks it, Alt H opens the next hint, Ctrl or Command slash toggles a line comment, Ctrl or Command Shift F formats the SQL, and Escape closes transient UI.
Cursor at line 1, column 1.
Scenario
Inspect schema metadata and small sample rows to name table grain, true identifiers, relationship keys, and result grain before writing relational SQL.
Tables, Rows, Columns, Keys, and Grain / predict result
One-sentence task
M01-A01 - Schema reasoning - match three tiny tables to row-grain statements. State row grain, distinguish identifiers from labels, and preview relationships.
Practice mode disclosure
Concise prompt, normal schema help, optional hints, and the same checker workspace are available.
Structured output contract
- Result grain
- one row per matched table
- Exact columns
- table_name; row_grain
- Source population
- Use the prompt setup plus FROM, JOIN, WHERE, and subquery predicates as the source population. Visible rows are only examples.
- Grouping
- Do not collapse rows unless the contract explicitly asks for aggregation, distinct tuples, or set semantics.
- Ordering
- match orders to one row per order header; order by table_name
- Validation
- select-only; hidden deterministic variants.
Relevant tables
Time and difficulty
- Estimated time
- 4 minutes
- Difficulty
- 1/5
Objective and concepts
Practice mode keeps the prompt concise; open hints only if you choose guided help.
Assumptions, dialect notes, and common traps
- Duplicate policy
- Preserve duplicate facts unless the prompt explicitly asks for distinct tuples or set semantics.
- Null policy
- Preserve NULL, empty string, zero, and false as distinct values unless the contract says to display a fallback.
- Tie-breakers
- Use every ordering rule in the contract and end tied business metrics with deterministic secondary keys when needed.
- Zero-related entities
- Do not invent zero rows unless the contract asks for preserved parents, missing entities, or complete periods.
- Numeric tolerance
- Use exact semantic comparison unless the activity explicitly declares a numeric tolerance.
Opened hints
No hints opened yet.