Struct bonsaidb::core::key::CompositeKeyFieldContainsNullByte

pub struct CompositeKeyFieldContainsNullByte;

Null bytes in variable fields encoded with CompositeKeyEncoder can cause sort order to misbehave.

Consider these tuples:

Tuple	Encoded
("a", "b")	9700 9800 0101
("a\0", "a")	9700 9700 0101

The encoded bytes, when compared, will produce a different sort result than when comparing the tuples.

By default, CompositeKeyEncoder checks for null bytes and returns an error when a null byte is found. See CompositeKeyEncoder::allowing_null_bytes() if you wish to allow null bytes despite this edge case.

Trait Implementations

impl Debug for CompositeKeyFieldContainsNullByte

fn fmt(&self, f: &mut Formatter<'_>) -> Result<(), Error>

Formats the value using the given formatter.

impl Display for CompositeKeyFieldContainsNullByte

fn fmt(&self, __formatter: &mut Formatter<'_>) -> Result<(), Error>

Formats the value using the given formatter.

impl Error for CompositeKeyFieldContainsNullByte

fn source(&self) -> Option<&(dyn Error + 'static)>

The lower-level source of this error, if any.

fn description(&self) -> &str

👎Deprecated since 1.42.0: use the Display impl or to_string()

fn cause(&self) -> Option<&dyn Error>

👎Deprecated since 1.33.0: replaced by Error::source, which can support downcasting

fn provide<'a>(&'a self, demand: &mut Demand<'a>)

🔬This is a nightly-only experimental API. (error_generic_member_access)

Provides type based access to context intended for error reports.