The ordering of values and rows for InfluxElixir.Client.Local's SQL, as
the engine orders them (verified against InfluxDB 3 Core): DateTimes
chronologically, numbers by InfluxElixir.Client.Local.SQLNumber (a
UInt64 or a decimal by its value, an infinity beyond every finite float),
nulls last when ascending and first when descending unless the query says
NULLS FIRST / NULLS LAST; it is not term order, which puts a nil before
every string and between false and true.
Summary
Functions
Where a direction puts nulls when the query does not say.
Stable multi-key sort with a direction per key.
One key's order: :before, :after or :tie.
Whether a sorts at or before b, ascending.
Types
@type key() :: {(term() -> term()), InfluxElixir.Client.Local.SQLClauses.direction()}
How one ORDER BY key reads a value from an item.
@type placement() :: {:asc | :desc, :nulls_first | :nulls_last}
A key's direction and where its nulls go.
Functions
@spec null_placement(InfluxElixir.Client.Local.SQLClauses.direction()) :: placement()
Where a direction puts nulls when the query does not say.
Stable multi-key sort with a direction per key.
Each item's key values are read once, not on every comparison, so the cost of a sort is its keys over the items and not over the comparisons.
One key's order: :before, :after or :tie.
Whether a sorts at or before b, ascending.