Which CROSSING a declared error covers — one IMPL FAMILY each, reached through the words the
field blocks already speak.
No new vocabulary: a declaration that writes sqlite(try_into = "…") on a field names
the crossing whose refusal sqlite(try_into(error = "…")) types, and the correspondence
is the word rather than a table a reader has to hold.
§persist names TWO of them, and a cell rides its LEG
A row’s read and its write are different impls with different callers — TryFrom<Row> for E and
TryFrom<E> for Row — so one cell over both would say either that they share an error or that
the question had not been asked. The BLOCK word is the same for the two and the LEG word is what
tells them apart, which is why as_str is not injective and why nothing reads it
to identify a cell: the identity is this enum’s own value.
The ROW’s WRITE leg — TryFrom<E> for <E><Db>, the impl the write lane spends, typed by
<db>(try_from(error = "…")).
It was a named refuse-until while nothing stored a record. query::sql::write is the consumer
it was waiting for: a record crosses to its row through SqlWrite::row and through nothing
else, so the type this cell names is what a caller catches when a column will not cross.
Every crossing, in the order the grammar lists them — the two persist legs first, read before
write, which is the order a declaration’s own block reads.