In terms of date ranges, there are some problems with actual-data-nodes

[linghengqian]

After the project was upgraded to 5.0.0-alpha, I thought, INTERVAL, if datetime-interval-unit chooses DAYS and datetime-interval-amount chooses 1, in this case, how should actual-data-nodes be written?

Is it difficult to avoid the issue of different days in February in leap years and peace years?

By analogy, if INTERVAL chooses DAYS for datetime-interval-unit and 7 for datetime-interval-amount, in this case, actual-data-nodes is also difficult to write in line expressions? Can someone provide an idea?

The best way to deal with dates I have seen is to map dates to natural numbers of 1, 2,...N as shown by AUTO_INTERVAL. There is no such problem in actual-data-nodes. But this and INTERVAL are completely two ideas.

After all, AUTO_INTERVAL does not have the attribute configuration of a logical table. When I want to extend AUTO_INTERVAL, I can only use CLASS_BASED.

In create discussion soon, I have created the same content of the new issue. Pointing to #13240

2021.10.27update:
I'm sorry I thought that auto-tables has no logical tables...this is my practice accident.

[linghengqian]

• This discussion is closed as the issue has been resolved.