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.
INSERT, UPDATE, DELETE, and RETURNING / predict result
M31-A01 - Prediction: INSERT, UPDATE, DELETE, and RETURNING
M31-A01 - Prediction: INSERT, UPDATE, DELETE, and RETURNING. Make targeted state changes and inspect affected rows inside rollback-safe checks.
- Result grain
- one row per active unassigned employee
- Exact columns
- employee_id; employee_name
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
Use the visible seed to understand the task, then pass hidden deterministic variants.
INSERT, UPDATE, DELETE, and RETURNING / predict result
One-sentence task
M31-A01 - Prediction: INSERT, UPDATE, DELETE, and RETURNING. Make targeted state changes and inspect affected rows inside rollback-safe checks.
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 active unassigned employee
- Exact columns
- employee_id; employee_name
- 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
- order by employee_id
- Validation
- select-only; hidden deterministic variants.
Relevant tables
Time and difficulty
- Estimated time
- 7 minutes
- Difficulty
- 4/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
- Preserve requested zero-related, no-match, or complete-period entities and make display fallback explicit.
- Numeric tolerance
- Use exact semantic comparison unless the activity explicitly declares a numeric tolerance.
Opened hints
No hints opened yet.