You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 18, 2024. It is now read-only.
We currently support timezones at logical level, via Timestamp(_, tz), but have no mechanism to perform operations with them, The goal is to investigate how to add support for them. This will likely require depending on chrono-tz.
A simple concrete goal here is to add support to cast from and to Timestamp(_, str) and Timestamp(_, None).
A question here is how we represent these things: it seems that in chrono-tz, timezones are static types (i.e. struct), while timezones in Arrow are dynamic (i.e. str).
The text was updated successfully, but these errors were encountered:
There has been some discussions over the mailing list on how timezones should be treated, so I have not touched this. It seems that they have settled, though.
We currently support timezones at logical level, via
Timestamp(_, tz)
, but have no mechanism to perform operations with them, The goal is to investigate how to add support for them. This will likely require depending on chrono-tz.A simple concrete goal here is to add support to
cast
from and toTimestamp(_, str)
andTimestamp(_, None)
.A question here is how we represent these things: it seems that in
chrono-tz
, timezones are static types (i.e. struct), while timezones in Arrow are dynamic (i.e.str
).The text was updated successfully, but these errors were encountered: