Update ClickBench queries to avoid to_timestamp_seconds

[acking-you]

Which issue does this PR close?

• Closes Update ClickBench queries to avoid to_timestamp_seconds #15465 .

Rationale for this change

What changes are included in this PR?

Are these changes tested?

Are there any user-facing changes?

[adriangb]

Looks good to me. Since we're only ordering by this it shouldn't matter that we order by an integer instead of a proper timestamp, ordering is equivalent.

[adriangb]

Should we update the same query in the clickbench repo as well?

[Dandandan]

Should we update the same query in the clickbench repo as well?

Yes, and we might rerun the queries as well (as to_timestamp_seconds takes some time itself as well).

[acking-you]

Looks good to me. Since we're only ordering by this it shouldn't matter that we order by an integer instead of a proper timestamp, ordering is equivalent.

Thank you very much for your reply, but I have a question: why can't the following order by "EventTime" be modified? It seems that they are equivalent (since the default is UTC timestamps). And both ClickHouse and duckdb do this way: duckdb clickhouse @adriangb

[adriangb]

Looks good to me. Since we're only ordering by this it shouldn't matter that we order by an integer instead of a proper timestamp, ordering is equivalent.

Thank you very much for your reply, but I have a question: why can't the following order by "EventTime" be modified? It seems that they are equivalent (since the default is UTC timestamps). And both ClickHouse and duckdb do this way: duckdb clickhouse

I'm agreeing with you! I think this change is good 😄

[acking-you]

I have also made changes to the query in ClickBench: clickbench-pr
@Dandandan @adriangb

[adriangb]

@Dandandan do you think we can merge this here?

[Dandandan]

Thank you @acking-you