|
23 | 23 | //! For the generated flat-scalar families, every payload has the shared envelope |
24 | 24 | //! keys (required by every scalar domain CHECK, mirroring `ENVELOPE_KEYS` in |
25 | 25 | //! `eql-domains`): `v`, `i`, `c`. Then the domain's required term keys — `hm` |
26 | | -//! for `_eq`, `ob` for `_ord`/`_ord_ore`, `op` for `_ord_ope`, `bf` for |
27 | | -//! `_match`, none for |
28 | | -//! storage-only. `Option` does not appear in the generated scalar structs: the |
| 26 | +//! for `_eq`, `op` for `_ord`/`_ord_ope`, `ob` for `_ord_ore`, `bf` for |
| 27 | +//! `_match` (and, alongside the ordering term, for the `_search` domains), |
| 28 | +//! none for storage-only. `Option` does not appear in the generated scalar structs: the |
29 | 29 | //! capability **is** the type identity. Hold a [`integer::IntegerEq`] and `hm` is |
30 | 30 | //! present, guaranteed by the Rust type and (SQL-side) by the domain CHECK. A |
31 | 31 | //! missing term key is a deserialization error — the Rust analogue of the CHECK |
32 | 32 | //! constraint. |
33 | 33 | //! |
34 | | -//! One exception to "`ob` for `_ord`": `text`'s ordered domains carry **both** |
35 | | -//! `hm` and the ordering term (`text_ord`/`text_ord_ore`/`text_search` carry |
36 | | -//! `hm` + `ob`; `text_ord_ope` carries `hm` + `op`), where the non-text |
| 34 | +//! One exception to "the ordering term alone": `text`'s ordered domains carry **both** |
| 35 | +//! `hm` and the ordering term (`text_ord`/`text_ord_ope` carry `hm` + `op`; |
| 36 | +//! `text_ord_ore` carries `hm` + `ob`; `text_search` carries `hm` + `op` + |
| 37 | +//! `bf`; `text_search_ore` carries `hm` + `ob` + `bf`), where the non-text |
37 | 38 | //! ordered domains carry the ordering term alone. Text routes `=`/`<>` |
38 | 39 | //! through `hm` rather than the ordering term because lexicographic ORE/OPE |
39 | 40 | //! over text is not equality-lossless, so equality needs the HMAC. The |
40 | 41 | //! generated struct doc surfaces this structurally — its required-keys line |
41 | | -//! lists `hm` `ob` (or `hm` `op`) rather than just the ordering key. |
| 42 | +//! lists `hm` `op` (or `hm` `ob`, plus `bf` for the `_search` domains) rather than |
| 43 | +//! just the ordering key. |
42 | 44 | //! |
43 | 45 | //! The generated flat-scalar types are also **strict**: every scalar struct is |
44 | 46 | //! `#[serde(deny_unknown_fields)]`, so a payload carrying keys outside the |
|
0 commit comments