SQL
Label the reading without replacing it
BOTIE
Examples, experiments and workspace controls
Connect a tool's inputs to see what it produces. You can try a branch before connecting it to Result.
Try your own inputs
Use a copy of the example to try your own data. Keep the problem's assumptions in mind, and predict the effect of a change before checking the output. You can also add another branch to compare two ways of doing the calculation.
Context for this challenge
Connect the readings and threshold to Label a measured threshold. Inspect the original value beside the new action field.
The dashboard needs a policy label while preserving the distinction between missing and measured values.
Inspect the component calculation
Label a measured threshold( Rows: Temperature readings Inspection threshold: 75 Measured field: temperature Label field: action )
Examples and results
- Temperature readings
[ { "reading_id": 1, "asset_id": "P1", "temperature": 70 }, { "reading_id": 2, "asset_id": "P1", "temperature": 80 }, { "reading_id": 3, "asset_id": "P2", "temperature": null }, { "reading_id": 4, "asset_id": "P3", "temperature": 65 } ]- Required result
[ { "reading_id": 1, "asset_id": "P1", "temperature": 70, "action": "monitor" }, { "reading_id": 2, "asset_id": "P1", "temperature": 80, "action": "inspect" }, { "reading_id": 3, "asset_id": "P2", "temperature": null, "action": "unknown" }, { "reading_id": 4, "asset_id": "P3", "temperature": 65, "action": "monitor" } ]
Try a fresh construction
This clears this draft, including its undo history. Earlier successful attempts stay recorded. Build again without opening hints to record an independent attempt.
Stuck? Inspect a worked construction
The tools below form one possible solution. You can assemble it, follow its signals, and undo that change to return to your own construction.
Assumptions and test precision
The workshop calculates over small record lists to make the relational operations visible. It is not a SQL parser or query planner. The worksheet runs SQLite and is the authority for SQL behaviour, including types and NULL. Numerical tests allow a difference of 0.001. Lists and structures must also have the right shape.
Your last tested pieces can start the full construction. An existing draft there keeps its own pieces.
Known readings fall on opposite sides
This check uses the pieces from “Apply the threshold without hiding missing data”.
BOTIE
- Temperature readings
[ { "reading_id": 9, "temperature": 74 }, { "reading_id": 7, "temperature": 76 }, { "reading_id": 8, "temperature": 0 } ]
Use a number, text, or an array matching the requested result. For a matrix, put each row in brackets. Saving your prediction runs your current construction on these inputs and checks the earlier examples too.
Build a construction in the workspace above first. This case will test those pieces.
If an emergency band were added, where would its overlapping condition belong relative to inspect?
The first true CASE branch determines the result, so overlapping policy order matters.
The workshop calculates over small record lists to make the relational operations visible. It is not a SQL parser or query planner. The worksheet runs SQLite and is the authority for SQL behaviour, including types and NULL.
Work through the SQL challenges →