Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve DateTime64 pushdown to ClickHouse #23789

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Commits on Oct 15, 2024

  1. Fix CTAS for Clickhouse TimestampWithTimeZone

    The time zone is not stored in the rows of the table,
    but is stored in the column metadata.
    
    From ClickHouse documentation
    https://clickhouse.com/docs/en/sql-reference/data-types/datetime
    
    The point in time is saved as a Unix timestamp, regardless of the time
    zone or daylight saving time. The time zone affects how the values of
    the DateTime type values are displayed in text format and how the values
    specified as strings are parsed (‘2020-01-01 05:00:01’).
    
    Timezone agnostic Unix timestamp is stored in tables, and the timezone
    is used to transform it to text format or back during data import/export
    or to make calendar calculations on the values (example: toDate, toHour
    functions etc.). The time zone is not stored in the rows of the table
    (or in resultset), but is stored in the column metadata.
    ssheikin committed Oct 15, 2024
    Configuration menu
    Copy the full SHA
    a111835 View commit details
    Browse the repository at this point in the history

Commits on Oct 16, 2024

  1. Support DateTime64 in ClickHouse

    TIMESTAMP(p)
    TIMESTAMP(p) WITH TIME ZONE
    ssheikin committed Oct 16, 2024
    Configuration menu
    Copy the full SHA
    c4c68c1 View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    0c80cf5 View commit details
    Browse the repository at this point in the history