Blog· Tested on ClickHouse 26.4

yesterday() and today() deserve a tomorrow()

ClickHouse has yesterday() and today() but no tomorrow(). I asked for it with a straight face and a marketing pitch. It is still missing, and today() + 1 does the job.

Source: github.com

ClickHouse has today() and yesterday() but no tomorrow(). The workaround is one token, today() + 1, so this is a small request, and I said so. My argument is that a named function states intent (WHERE event_time < tomorrow()) and that a gap in a family of names is something people have to remember. I also padded the issue with a pitch about forecasting pipelines, which was mostly marketing.

Nothing from the maintainers. The issue is open with the labels feature, comp-datetime and external and no comments. An automated coding assistant opened PR #92054 the same month; it was closed without merging on 2026-01-30 after CI failures.

On 26.4 SELECT tomorrow() fails with UNKNOWN_FUNCTION. A SQL user-defined function gives you the name today, with the caveat that it will collide if a built-in ever arrives:

CREATE FUNCTION tomorrow AS () -> today() + 1;
SELECT tomorrow();

For what SQL UDFs can and cannot do, see what ClickHouse UDFs should be able to do. I am fine if this stays open: even a trivial function costs a review, a documentation page and a place in a namespace every user shares.

feature-requestdatetimefunctions

Discussion

Comments live in GitHub Discussions. Sign in with GitHub to join in.