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
Use Timestamp as the default type for detected date time objects
Removes a lot of the strategy logic and simplifies the overall mapping
Use Timestamp(..., Some("UTC")) for UTC times
Use Timestamp(..., None) for naive date times
Use Date64 for naive dates
Remove the strategy logic
Note: Date64 is incorrectly used to represent timestamps, it should actually be date and count the number of days ("values of Date64 are treated as the number of days, in milliseconds, since the UNIX epoch. Therefore, values of this type must be evenly divisible by 86_400_000, the number of milliseconds in a standard day.")
The text was updated successfully, but these errors were encountered:
chmp
changed the title
[brekaing] Switch to Timestamp as the default type for deteteced date time objects, make Date64 naive only
[breaking] Fix Date64 semantics
Oct 4, 2024
Use
Timestamp
as the default type for detected date time objectsRemoves a lot of the strategy logic and simplifies the overall mapping
Timestamp(..., Some("UTC"))
for UTC timesTimestamp(..., None)
for naive date timesDate64
for naive datesThe text was updated successfully, but these errors were encountered: