Row 11208

Here is Case, as the filing cabinet sees Case.

The drawer is a tableConcept · lights on your maptableA store of information about one category of thing (orders, runners, entries), built from rows and columns. The rows are the individual items; the columns define what gets recorded about each.: one category of thing, held in a grid. The registrations table holds registrations and nothing else. Runners have their own table, results will have theirs, and keeping the categories in separate drawers is the first discipline of the whole design.

Case is a rowConcept · lights on your maprowOne item stored in a table: a single runner, a single entry. Engineers also say record. Rows supply the values; columns say what the values mean., one horizontal line of the grid. Every fact the form collected sits in that line, each under a columnConcept · lights on your mapcolumnOne type of information recorded for every row in a table (the email column, the estimate column), usually with an expected data type. Engineers also say field.: name, date of birth, email, estimated finish. Twenty-five thousand accepted entries, twenty-five thousand rows, all wearing exactly the same columns, which is what structured meant last scene.

The rules of the grid

What keeps the grid honest is the schemaConcept · lights on your mapschemaThe defined structure and rules of a database: which tables exist, which columns each has, each column’s type, what is required, what must be unique, how tables connect. An enforced system of expectations, though it enforces only rules actually written down.: the written constitution saying which tables exist, what each column holds, what may never be empty, what must never repeat. The payload from Act I could be trusted partly because this constitution was waiting for it. A birthdate goes in the birthdate column typed as a date, and the database itself, below every app and every check you have met so far, will refuse a word there.

The schema is also why one entry per person had teeth. The email column carries a written rule, must be unique, and a rule enforced by the cabinet cannot be talked out of anything by a clever client. Act I called the server-side the law. This is the law’s law.

One thing in the line above is doing quiet, heavy work: the bib number. Why 11208 and not the email, and what happens when tables need to point at each other, is the next scene.