---
title: `ceiling`
url: https://nexyron.tech/docs/cypher/functions/numeric/ceiling
description: Is the ceil alias that rounds a numeric value up to the next integer boundary. It is documented separately because numeric transforms change ranking, thresholds, and buckets in w
---

# `ceiling`

## Generic Description

Is the `ceil` alias that rounds a numeric value up to the next integer boundary. It is documented separately because numeric transforms change ranking, thresholds, and buckets in ways planner tools must not guess.

Simple example:

```cypher
RETURN ceiling(2.1) AS value
```

## Consumer-Level Explanation

Use it when a query should expose the SQL-style spelling while keeping the same bucket semantics as `ceil`. 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

`ceiling` 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 `ceiling` to a named score component after matching graph data, making the derived metric reviewable before ordering.

```cypher
MATCH (d:Document)
WITH d, properties(d).prize / 1.5 AS normalized_priority
RETURN d.title AS document,
       ceiling(normalized_priority) AS priority_band
ORDER BY 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