I got some help on SO help this morning working with timezones in lubridate. My problem was that the lubridate functions appear to only accept a timezone of length 1, and I had a situation where I wanted to convert a bunch of strings in one data frame column to a timezone specified in another column.
The answerer suggested wrapping the
mutate call in
ungroup, which works great! But it’s not intuitive, and I’m wondering how performant it would be on large datasets. It would be great if the
tz arguments in
force_tz and others used
tidyeval as well so that a column could be specified for them.
I also noticed while working on this problem that when tibbles with date-time columns are printed, they print using one of the time zones in the column—I think maybe the latest time zone in the column or the tibble? This was a little unintuitive to me: I expected that they would print using either UTC or my local time zone. Does anyone know if there’s any way to configure this behaviour?