Subject: [DISCUSS] Support year-month and day-time Intervals


Introducing a new data type has high overhead, both in terms of internal complexity and users' cognitive load. Introducing two data types would have even higher overhead.

I looked quickly and looks like both Redshift and Snowflake, two of the most recent SQL analytics successes, have only one interval type, and don't support storing that. That gets me thinking in reality storing interval type is not that useful.

Do we really need to do this? One of the worst things we can do as a community is to introduce features that are almost never used, but at the same time have high internal complexity for maintenance.

On Fri, Jan 10, 2020 at 10:45 AM, Dongjoon Hyun < [EMAIL PROTECTED] > wrote: