Reading diagrams / Topic 24 of 42
Where the handle comes from
The rule
Code that touches a database needs a handle to it. The map shows where each handle comes from.
A blue rail along the bottom of the wall is a handle handed in from outside, rising to every use. Where the rail starts, the word platform means no definition in the program can make one, so the runtime does.
A plus-disc under a ring, labelled with a call such as “notes_table()”, is a handle the code builds right there. A pale ? beside a mark means Yichus did not follow that use's handle back to where it comes from; the rail's db label keys it once as “not followed”. Where the rail starts at platform, nothing in the program or its libraries can make a database handle, so a use marked ? still gets its database from outside: the ? says only that Yichus did not follow which table it opens on it. Where the rail starts at a ?, the program could make one, and the map can't tell how a use marked ? gets its handle.
notes-api and notes-api-local have the same routes and the same tables. Only the handles differ, and only the bottom of the wall shows it.
- Rail to every use: handed in. Plus-disc: built here.
- A ? on a use under a rail that starts at platform: its database is still handed in. Under a rail that starts at ?, the map can't tell.
notes-api.
Loading the system map.
notes-api-local: the same routes, written another way.
Loading the system map.
policy-docs.
Loading the system map.
How to read this: what each mark in these pictures means
Loading the worked examples and practice.