> ## Documentation Index
> Fetch the complete documentation index at: https://kumo.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# LIST_DISTINCT

#### `LIST_DISTINCT(<table>.<column>, <start>, <end>, <unit>)`

## Description

Generates a list of all distinct values in the specified `<table>.<column>` column starting from `<start>` days to `<end>` days. When used in the target field, the time period should be positive (in the future). When used in a temporal filter field, the time period should be negative (in the past).

This operator can be applied to columns of any type.

For an optimal user experience, Kumo recommends limiting the use of `LIST_DISTINCT` to cases where the number of possible return values is less than 1000.

### Example

<CodeGroup>
  ```Text PQL theme={null}
  LIST_DISTINCT(LOAN.AMOUNT, 0, 30)
  ```
</CodeGroup>

### Training Considerations

* Kumo runs your pQuery over many historic slices of data and across all entities that meet your filter criteria to generate training examples.
* If for a given entity and historic data slice there are no fact rows to aggregate over, this training example will be dropped. Thus, the operator makes the implicit assumption that for every entity a prediction is generated for, that entity has at least one fact row in the prediction horizon. If you would like to predict periods with no interactions, you may use the `IS NULL` or `IS NOT NULL` operators.
* For all aggregations, the start time is **excluded** from the calculation and the end time is **included** in the calculation.
* The units for the start and end times is `days` by default but can be specified as `months` or `hours`.