Given that we support CURRENT_TIMESTAMP, the lack of CURRENT_DATE feels like an omission. While you can hack it with date(now), I keep finding myself wishing there was a direct way to reference this. Given that now means CURRENT_TIMESTAMP, I think there's precedent for today meaning CURRENT_DATE. This is supported by all backends we support (and is in the ISO standard I believe).

This custom prompting implementation (built around input()) could easily be replaced by click.prompt:
https://github.com/aiidateam/aiida-core/blob/0e17ac1d35d3e90b7277fbfe2fa0edabc9732b53/aiida/manage/backup/backup_utils.py#L19-L126

At least it seems well tested, though
https://codecov.io/gh/aiidateam/aiida-core/src/develop/aiida/manage/backup/backup_utils.py

Through the 'case when' statement of /console/druid/ page, json is obtained:
`{
"queryType": "groupBy",
"dataSource": {
"type": "table",
"name": "dw_action_sec_data_test"
},
"intervals": {
"type": "intervals",
"intervals": [
"-146136543-09-08T08:23:32.096Z/146140482-04-24T15:36:27.903Z"
]
},
"virtualColumns": [],
"filter": null,
"granularity