-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Timezone UTC
is not considered equal to +00:00
#10957
Comments
Probably this is the reason why...both |
Technically |
I'd be happy to create a pool to start adding special cases, but that sounds like a rabbit hole. |
I think the chrono-tz crate has the special cases / knows how to handle converting "UTC" to "+0:00" so I don't think we would have to make a special datafusion map The arrow crate has a "chrono-tz" feature which activates it. I wonder if we have to turn that on somewhere 🤔 https://crates.io/crates/arrow or maybe use an appropriate check in datafusion |
I am responding to @marvinlanhenke 's comment #10960 (comment)
I think that So perhaps we could update the timezone comparison check to compare those two types the same 🤔 |
#10960 from @marvinlanhenke is up for review 🙏 |
Describe the bug
Running
Results in an error:
As far as I know UTC is alwasy identical to
+00:00
so these two should be considered equivilant?To Reproduce
No response
Expected behavior
Timezones which are practically equivalent — e.g. have the same offset and DST semantics should allow subtraction to get an interval.
Additional context
No response
The text was updated successfully, but these errors were encountered: