Implemented Adbc.Column.interval/3

[cocoa-xu]

No description provided.

[josevalim]

Wait, so they have both duration and interval? :(

In any case, it seems interval better mirrors Elixir's duration, although we don't have to support it right now!

[cocoa-xu]

In any case, it seems interval better mirrors Elixir's duration,

Yeah, I was think about to use Duration but my main hesitancy with using Duration is that Arrow's interval would only use some components, i.e., for data type NANOARROW_TYPE_INTERVAL_MONTH, the result value will only use the month field, while for the NANOARROW_TYPE_INTERVAL_DAY_TIME type, the result value will only use day and microsecond.

The worst part is, there's no conversion rule in arrow to convert from one type of interval to another -- which means if the user passes Adbc.Column.interval(Duration.new!(day: 60), :month) to us, it will turn out to be 0.

To address this, we might either note it in the inline docs. But some users are probably going to be confused why there is data loss if they assumed there're some kind of conversions. Or we can check every Duration and raise if unused fields are not 0 -- however this definitely has a performance penalty.

although we don't have to support it right now

Let's let future us deal with this XD