← All workshopsRead Let a Search Value Stay a Value

SQL

Match a search inside the trusted tenant scope

BOTIE

Connect all jobs and the trusted scope selector to Match every named selector field. Inspect the scoped rows before applying the search.
Ready to test
0 passed · 0 failed · 2 not run

An empty floor. Start with the information your machine needs.

Received result

Your answer will arrive here.

Examples, experiments and workspace controls
Live values

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.

Start at an output arrow, then click or drag to an input. Drag empty space to pan. Delete removes a selection. Ctrl/Cmd+Z undoes a change.
Context for this challenge

Connect all jobs and the trusted scope selector to Match every named selector field. Inspect the scoped rows before applying the search.

Two tenants use the same local asset label.

Inspect the component calculation
Match every named selector field(
  Records: Job records
  Exact selector: Trusted tenant selector
)
Examples and results
Job records
[
  {
    "id": "J1",
    "tenant": "north",
    "asset": "P7"
  },
  {
    "id": "J2",
    "tenant": "south",
    "asset": "P7"
  }
]
Trusted tenant selector
{
  "tenant": "north"
}
Required result
[
  {
    "id": "J1",
    "tenant": "north",
    "asset": "P7"
  }
]
Job records
[
  {
    "id": "J1",
    "tenant": "north",
    "asset": "P7"
  }
]
Trusted tenant selector
{
  "tenant": "north"
}
Required result
[
  {
    "id": "J1",
    "tenant": "north",
    "asset": "P7"
  }
]
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 widget has no SQL parser and no real login. The Python challenge exercises parameter binding; production permissions need a deployed service design. 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.

The quoted asset exists inside one tenant

This check uses the pieces from “Search inside the trusted scope”.

BOTIE

The exact asset value P'2 belongs to jobs in two tenants. Trusted scope is east. Predict the visible ID while keeping the quote as data.
Job records
[
  {
    "id": "J8",
    "tenant": "east",
    "asset": "P'2"
  },
  {
    "id": "J9",
    "tenant": "west",
    "asset": "P'2"
  }
]
Trusted tenant selector
{
  "tenant": "east"
}
Supplied asset value
{
  "asset": "P'2"
}

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.

Why does binding a tenant value as a parameter not prove the caller may choose that tenant?

Keep query structure, parameter values and authorisation decisions at separate boundaries.

The widget has no SQL parser and no real login. The Python challenge exercises parameter binding; production permissions need a deployed service design.

Work through the SQL challenges →
Continue the courseWhich Sensor Records Should Reach the Training Table? →
← Why Does a Short Query Repeat So Much Work?