MarcoGorelli commented on issue #36558: URL: https://github.com/apache/arrow/issues/36558#issuecomment-1799366174
To be honest I'm hoping Arrow won't support fixed offsets For individual elements, sure, they're well defined and unambiguous. `'2020-01-01T01:12:34+05:00'` is unambiguous But if you're working with timezone-aware data, you're presumably working with a real-world problem - in which case, nudging you towards using the `Area/Location` time zone identifier will prevent you from ending up with daylight-saving-time-related issues if you'd mistakenly used a fixed offset For example, '2023-02-16T17:19:02+02:00' could be both 'Europe/Sofia' (which observes daylight saving time) or 'Africa/Johannesburg' (which doesn't observe daylight saving time). The individual timestamp is allowed to have `+02:00`, but letting the dtype of the array be a fixed offset sounds like a user bug waiting to happen -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: github-unsubscr...@arrow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
