---
title: `pow`
url: https://nexyron.tech/docs/cypher/functions/numeric/pow
description: Raises a numeric base to a numeric exponent. It is documented separately because numeric transforms change ranking, thresholds, and buckets in ways planner tools must not guess.
---

# `pow`

## Generic Description

Raises a numeric base to a numeric exponent. It is documented separately because numeric transforms change ranking, thresholds, and buckets in ways planner tools must not guess.

Simple example:

```cypher
RETURN pow(2.0, 3.0) AS value
```

## Consumer-Level Explanation

Use it when scores need explicit nonlinear weighting rather than an opaque client-side formula. 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

`pow` 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 `pow` 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 AS priority
RETURN d.title AS document,
       pow(priority, 2.0) AS squared_priority
ORDER BY squared_priority 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