Skip to main content
These settings are autogenerated from source.

​
date_time_64_output_format_cut_trailing_zeros_align_to_groups_of_thousands

Dynamically trim the trailing zeros of DateTime64 values, rounding the output scale up to the next multiple of three that keeps every significant digit: [0, 3, 6, 9]. An all-zero fraction is dropped.

​
date_time_input_format

Allows choosing a parser of the text representation of date and time. The setting does not apply to date and time functions. Possible values:
  • 'best_effort' — Enables extended parsing. ClickHouse can parse the basic YYYY-MM-DD HH:MM:SS format and all ISO 8601 date and time formats. For example, '2018-06-08T01:02:03.000Z'.
  • 'best_effort_us' — Similar to best_effort (see the difference in parseDateTimeBestEffortUS
  • 'basic' — Use basic parser. ClickHouse can parse only the basic YYYY-MM-DD HH:MM:SS or YYYY-MM-DD format. For example, 2019-08-20 10:18:56 or 2019-08-20.
See also:

​
date_time_output_format

Allows choosing different output formats of the text representation of date and time. Possible values:
  • simple - Simple output format. ClickHouse output date and time YYYY-MM-DD hh:mm:ss format. For example, 2019-08-20 10:18:56. The calculation is performed according to the data type’s time zone (if present) or server time zone.
  • iso - ISO output format. ClickHouse output date and time in ISO 8601 YYYY-MM-DDThh:mm:ssZ format. For example, 2019-08-20T10:18:56Z. Note that output is in UTC (Z means UTC).
  • unix_timestamp - Unix timestamp output format. ClickHouse output date and time in Unix timestamp format. For example 1566285536.
See also:

​
date_time_overflow_behavior

Defines the behavior when Date, Date32, DateTime, DateTime64, Time, Time64 or numeric values (integers and floating-point numbers) are converted into Date, Date32, DateTime, DateTime64, Time or Time64 but the value cannot be represented in the result type. Decimal values can be converted only into DateTime64 and Time64, and those conversions follow this setting as well; a Decimal converted into Date, Date32, DateTime or Time is rejected regardless of the setting. It also applies when a Date or DateTime is parsed from text, including by an input format. Possible values:
  • ignore — Silently ignore overflows. For conversions between date and time types the result is undefined (the value may wrap around); a numeric value is saturated to the range boundaries of the result type.
  • throw — Throw an exception in case of overflow.
  • saturate — Saturate the result. If the value is smaller than the smallest value that can be represented by the target type, the result is chosen as the smallest representable value. If the value is bigger than the largest value that can be represented by the target type, the result is chosen as the largest representable value.
The accurate casts (accurateCast, accurateCastOrNull, accurateCastOrDefault) do not depend on this setting: an unrepresentable value is always rejected, reported as NULL or replaced with the default value, respectively. The setting applies to conversions done by CAST and the conversion functions, including those an INSERT ... VALUES expression template or an INSERT ... SELECT performs. A constant expression that the Values format evaluates without a template (the fallback enabled by input_format_values_interpret_expressions) and the values table function follow it only for DateTime64 and Time64: an out-of-range number put into a Date, Date32, DateTime or Time column there does not follow this setting. The values table function rejects it, and the Values format rejects it too, unless input_format_null_as_default is enabled, in which case it inserts the default value of the column. Default value: ignore.
Last modified on October 11, 2026