Interval

    Warning

    data type values can’t be stored in tables.

    • Time interval as an unsigned integer value.
    • Type of an interval.

    Supported interval types:

    • SECOND
    • MINUTE
    • HOUR
    • WEEK
    • MONTH
    • QUARTER
    • YEAR

    For each interval type, there is a separate data type. For example, the DAY interval corresponds to the data type:

    1. ┌─toTypeName(toIntervalDay(4))─┐
    2. │ IntervalDay                  │
    3. └──────────────────────────────┘
    1. │ 2019-10-23 10:58:45 │           2019-10-27 10:58:45 │
    2. └─────────────────────┴───────────────────────────────┘

    Intervals with different types can’t be combined. You can’t use intervals like 4 DAY 1 HOUR. Specify intervals in units that are smaller or equal to the smallest unit of the interval, for example, the interval 1 day and an hour interval can be expressed as or 90000 SECOND.

    You can’t perform arithmetical operations with Interval-type values, but you can add intervals of different types consequently to values in Date or DateTime data types. For example:

    1. ┌───current_date_time─┬─plus(plus(now(), toIntervalDay(4)), toIntervalHour(3))─┐
    2. │ 2019-10-23 11:16:28 │                                    2019-10-27 14:16:28 │
    3. └─────────────────────┴────────────────────────────────────────────────────────┘
    1. Received exception from server (version 19.14.1):
    2. Code: 43. DB::Exception: Received from localhost:9000. DB::Exception: Wrong argument types for function plus: if one argument is Interval, then another must be Date or DateTime..

    See Also

    • type conversion functions