reddb-io-types 1.24.10

RedDB logical type system: the neutral keystone vocabulary — Value, DataType, SqlTypeName, TypeModifier, TypeCategory, ValueError, Row — depended on by every authority crate and depending on none.
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69

//! `reddb-io-types` — the neutral keystone crate for RedDB's logical type
//! system (ADR 0052).
//!
//! This crate sits at the **bottom of the workspace crate graph**: every
//! authority crate (`reddb-io-file`, `reddb-io-wire`, the planned
//! `reddb-io-rql` and `reddb-io-crypto`) may depend on it, but it depends on
//! **no other workspace crate**. It owns the core type vocabulary —
//! [`Value`], [`DataType`], [`SqlTypeName`], [`TypeModifier`],
//! [`TypeCategory`], [`ValueError`], and [`Row`] — together with the
//! [`value_codec`] serialization that `Value::to_bytes`/`from_bytes` delegate
//! to.
//!
//! The `reddb-server` `storage::schema` module no longer re-exports this
//! vocabulary; every server, test, and driver call site names this crate
//! directly.

// The byte-faithful re-home (ADR 0052) preserves `types`/`value_codec`
// exactly as they were authored under the server's crate-level
// `#![allow(unused_imports)]`. `types.rs` keeps `std::net::{Ipv4Addr,
// Ipv6Addr}` in its module-level `use` even though the non-test paths
// reference them fully-qualified and the test module re-imports them
// locally; carrying the allow here keeps the move a pure relocation.
#![allow(clippy::unwrap_used)]
#![allow(unused_imports)]
// Legacy allow for the too_many_lines ratchet (PRD #1252): pre-existing
// codec/type functions exceed the 120-line threshold. The lint bites on
// new/changed code; remove once those functions are split up.
#![allow(clippy::too_many_lines)]
// Legacy allow for the cast_possible_truncation ratchet (PRD #1252):
// pre-existing codec/coercion functions truncate via `as` on lengths and
// numeric narrowing. The lint bites on new/changed code; remove once those
// casts become explicit checked conversions.
#![allow(clippy::cast_possible_truncation)]

pub mod canonical_key;
pub mod cast_catalog;
pub mod catalog;
pub mod coerce;
pub mod coercion_spine;
mod conversions;
pub mod distance;
pub mod document_body_codec;
pub mod duration;
pub mod encoding;
pub mod function_catalog;
pub mod index_hint;
pub mod json;
pub mod key_dictionary;
pub mod knowledge;
pub mod operator;
pub mod operator_catalog;
pub mod parametric;
pub mod polymorphic;
pub mod queue_mode;
pub mod serde_json;
pub mod table;
pub mod types;
pub mod utils;
pub mod value_codec;
pub mod value_compare;
pub mod value_json;
pub mod vector_metadata;

pub use canonical_key::{value_to_canonical_key, CanonicalKey, CanonicalKeyFamily};
pub use operator::BinOp;
pub use table::{
    ColumnDef, Constraint, ConstraintType, IndexDef, IndexType, TableDef, TableDefError,
};
pub use types::{DataType, Row, SqlTypeName, TypeCategory, TypeModifier, Value, ValueError};