resolve_value
Resolves a phrase, code, or spelling against a column's published values to return the stored spelling needed in a filter, or the closest matches when no exact value exists.
Instructions
Resolve a phrase, a code or a spelling against one column's published values, before writing a literal into a filter whose stored spelling get_table_context does not already list in full. Answers, in order of preference: stored - the text is a listed value, or folds to one, and the reply carries the spelling a predicate must use; definition - the text names what a value's note says it means; nearest - the listed values closest to the text, ranked; none; or unavailable where the column publishes no value list, lost it on the latest print, or redacts it. Every reply carries the column's coverage and how many values the print listed, plus a caveat sentence wherever that list is a sample - a spelling absent from a sample is not evidence it is absent from the column. An exhaustive list of at most fifty values rides along whole as domain, so a small vocabulary needs one call; on a table read in part, exhaustive is false, the reply carries the table's scope and row_count, and domain is the scanned rows' whole domain. Paged: every page repeats the scalar keys; the answer list comes before domain.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| part | No | A part of the column, by its path as the print keys it (`.status`, `[*]`); omit it to resolve against the column itself | |
| text | Yes | The phrase, code or spelling from the question, as written | |
| table | Yes | Fully-qualified table name | |
| column | Yes | Column name as the print spells it | |
| cursor | No | `next_cursor` from this call's previous page; omit for the first page | |
| connection | No | Which database to read, by connection name; needed only when the server serves several, and the error for a missing one lists them. Omit it for the server's default |