Macros

MACRO() turns a feature expression into a reusable function. You specify which inputs become parameters, and the result is a callable that you can invoke with different values — like defining a function in any programming language.

MACRO(expression USING param1, param2, ...)

Creating and calling a macro

Define a feature expression, then wrap it in MACRO() to make it callable. Here, AREA_CIRCLE_FEATURE computes the area of a circle, and AREA_CIRCLE_FUNCTION turns it into a function that accepts a radius:

WITH
    radius := INPUT(DOUBLE),
    area_circle_feature := PI() * POW(radius, 2e0),
    area_circle_function := MACRO(area_circle_feature USING radius)
SELECT
    area_circle_value_for_2 := "AREA_CIRCLE_FUNCTION"(2e0),
    area_circle_value_for_5 := "AREA_CIRCLE_FUNCTION"(5e0)
;

The macro is called like a regular function — AREA_CIRCLE_FUNCTION(2e0) evaluates the area formula with radius 2.

Inline expressions

You don't need to name the intermediate feature. The expression can go directly inside MACRO(), and arguments can be expressions too:

WITH
    radius := INPUT(DOUBLE),
    area_circle_function := MACRO(PI() * POW(radius, 2e0) USING radius)
SELECT
    area_circle_value_for_2 := "AREA_CIRCLE_FUNCTION"(1e0 + 1e0),
    area_circle_value_for_5 := "AREA_CIRCLE_FUNCTION"(2.5e0 * 2e0)
;

Multiple parameters

Macros accept any number of input parameters. The order of parameters in the USING clause determines the argument order when calling:

WITH
    length := INPUT(DOUBLE),
    width := INPUT(DOUBLE),
    area_rectangle_function := MACRO(length * width USING length, width)
SELECT
    area_rectangle_value_for_2_5 := "AREA_RECTANGLE_FUNCTION"(2e0, 5e0),
    area_rectangle_value_for_5_3 := "AREA_RECTANGLE_FUNCTION"(5e0, 3e0)
;

Chaining syntax

Macros support FeatureQL's chaining syntax. The chained value becomes the first argument:

WITH
    radius := INPUT(DOUBLE),
    area_circle_function := MACRO(PI() * POW(radius, 2e0) USING radius)
SELECT
    area_circle_value_for_2_chaining := 2e0."AREA_CIRCLE_FUNCTION"()
;

2e0.AREA_CIRCLE_FUNCTION() is equivalent to AREA_CIRCLE_FUNCTION(2e0).

Limitations

Macros are not polymorphic — each input parameter accepts only the type declared in its INPUT() definition. If you need a function that works across multiple types (e.g., both DATE and TIMESTAMP), use a UDF instead.

When to use macros vs variants

See Variants for dependency replacement and UDFs for polymorphic custom functions.