pub fn strategy_fields() -> Vec<Field>Expand description
The columns rudb_strategies() produces.
Named here rather than in the executor because the binder resolves the call and the executor fills it, and a table whose two halves disagree about its own columns is a bug that shows up as a wrong answer rather than as a compile error.
Nine columns and every one of them earns its place at a seam that has no implementations yet,
which is twenty six of the twenty seven today. seam, milestone and seam_description say
what the seam is and which milestone owes it its first two implementations, and they are filled
whether or not anything is registered. The other six describe an implementation and are null
when there is none, which is how the table says that a seam is planned rather than built without
anybody having to read a design document to find out.