Scenario: a fingerprint gets executed 1k times per day.
On statement_activity, we are able to keep the data for that fingerprint for 2 days.
On statement_statistics we had data for several days, but the limit of the table was reached, so older data had to be deleted and now only data for the past day is available.

If a user selects see past day: it will return the results from statement_activity, since the selected period existed there, and we will show 2k.
If a user selects past week: the statement_activity doesn't have this entire period, so it will return the results from statement_statistics, and that only had the last day, so it will return 1k.

So for the user, it shows past day 2k and past week 1k, which is confusing.
We need to improve this experience.

Possible solution:

• Delete the data based on TTL and have the same value for all tables
• Some union when the main table is selected
• Show warning/info message.

Jira issue: CRDB-30734