floor

Generic Description

Rounds a numeric value down to the previous integer boundary. It is documented separately because numeric transforms change ranking, thresholds, and buckets in ways planner tools must not guess.

Simple example:

RETURN floor(2.9) AS value

Consumer-Level Explanation

Use it for stable lower buckets such as score bands, hour buckets, or risk tiers. Prefer this function when the transformation is a deliberate part of the model or report, and name the derived value in a WITH stage when it will be reused.

More Detailed Explanation

floor is scalar math, so it is evaluated per row after graph patterns, procedure output, or map projections have produced values. Keep it close to the query when thresholds, ranking, and derived fields need to be auditable and reproducible.

Advanced Example

This example applies floor to a named score component after matching graph data, making the derived metric reviewable before ordering.

MATCH (d:Document)
WITH d, properties(d).prize / 1.5 AS normalized_priority
RETURN d.title AS document,
       floor(normalized_priority) AS lower_priority_band
ORDER BY lower_priority_band DESC

Real Use Cases

• distance-from-target scoring
• numeric bucketing and normalization before ORDER BY or aggregation
• making scoring formulas visible to query review and assistant tooling

Real Limitations And Tradeoffs

• invalid numeric inputs produce null-like results rather than a repaired value
• math functions do not fix poor feature scaling; choose transformations intentionally
• nondeterministic functions such as random sampling are not appropriate for persisted decisions