Curtis Vogt

> I also haven't added tests for `Quarter` because it's not clear to me how to get around the fact that this type was only introduced in Julia v1.6. Any...

> One thing to consider with this addition is that Arrow.jl doesn't handle type changes very well. I'm going to run a couple experiments with this today and either merge...

Looks like the parametric information isn't being stored which is problematic: ```julia julia> using Arrow julia> using Dates, Intervals, TimeZones julia> table = (interval = [ Interval{Closed,Closed}(1,2), Interval{Open,Closed}(1,2), Interval{Closed,Unbounded}(1,nothing), ],)...

I've made issues with Arrow for the two problems I've discovered: - https://github.com/JuliaData/Arrow.jl/issues/134 - https://github.com/JuliaData/Arrow.jl/issues/135

I'll also note this is the terminology used by PostgreSQL's range functions: https://www.postgresql.org/docs/9.3/functions-range.html

As moving between `DateTime` and `ZonedDateTime` isn't lossless there definitely needs to be some user input to make this transition. Could you provide more context into why you want this...

> Our use case is that we need to work around JuliaTime/TimeZones.jl#271 It would be great to find a path forward on that. As you're already working with switching to...

> Yeah, that's the main reason why I didn't want to get into it. Fair enough. It helps seeing the bigger picture to figure out a better path forward. >...

One other thing to mention here is there is also a type associated with the lower/upper endpoint which represents the type of bound used (closed/open/unbounded). The terms `lowerbound`/`upperbound` may lead...

An attempt to address this: https://github.com/invenia/Intervals.jl/pull/143