Re^4: Question regarding Time::Piece and timezones

I am also curious as to what happens with these ambiguous local times, like in the US 1:23 AM can occur twice during the same day.

What...? Anyway, see the %p and %P tokens.

Invalid offset: CST

As per DateTime::Format::Strptime: "By default, the parser will die when it parses an ambiguous abbreviation."

$ perl -wMstrict -MDateTime -le 'print DateTime->now(time_zone=>$_)->s
+trftime("%Z %z") for qw# America/Havana Asia/Shanghai America/Chicago
+ #'
CST -0500
CST +0800
CST -0600
[download]

Also occasionally a specific location can change its time zone - the International Date Line was moved some years back - this affected some islands in the Pacific.

Hence the existence of location-based time zone names that are unambiguous in that respect.

$ perl -wMstrict -MDateTime -le 'print DateTime->new(year=>$_,time_zon
+e=>"Pacific/Apia")->strftime("%Y %z") for qw/ 2010 2012 /'
2010 -1100
2012 +1400
[download]

Comment on Re^4: Question regarding Time::Piece and timezones Select or Download Code

Replies are listed 'Best First'.
Re^5: Question regarding Time::Piece and timezones by hippo (Bishop) on Jan 22, 2021 at 15:13 UTC
What...? Daylight Saving. 🦛	[reply]
Re^6: Question regarding Time::Piece and timezones by haukex (Archbishop) on Jan 22, 2021 at 16:17 UTC
Daylight Saving. Hm, yes, true if one reads the question without the context of the rest of the thread. My confusion stems~~med~~ from the fact that the thread includes YMD and time zone names that would normally resolve that ambiguity. Update: Of course the time zone names used in the following are still ambiguous in other ways, as per my post above. Update 2&3: Upon rereading: the "in the US" bit is still confusing me, since this ambiguity is true of any time zone that observes DST, hence my assumption that this had something to do with AM/PM rather than DST. Other minor reformatting. use warnings; use strict; use DateTime::Format::Strptime; my $strp = DateTime::Format::Strptime->new( pattern => '%F %H:%M %P %Z', on_error => 'croak', zone_map => { CST => '-0600', CDT => '-0500' } ); for my $str ('2020-03-08 1:23 AM CST','2020-03-08 1:23 AM CDT') { print $str, " = "; my $dt = $strp->parse_datetime($str); $dt->set_time_zone('UTC'); print $dt->strftime('%F %T %Z'), " = "; $dt->set_time_zone('America/Chicago'); print $dt->strftime('%F %T %Z'), "\n"; } __END__ 2020-03-08 1:23 AM CST = 2020-03-08 07:23:00 UTC = 2020-03-08 01:23:00 + CST 2020-03-08 1:23 AM CDT = 2020-03-08 06:23:00 UTC = 2020-03-08 00:23:00 + CST [download]	[reply] [d/l]
Re^5: Question regarding Time::Piece and timezones by Marshall (Canon) on Jan 23, 2021 at 02:44 UTC
I guess that what this nets out to, is that if you log a "local time", you also need the time_zone. I am in the US Pacific Time Zone (PST). Once per year, a "day" will have 25 hours. My wristwatch will wind up showing 1:15 AM twice during that day. It is Ok that 1:15 AM PST and 1:15 AM PDST converts to a different GMT time, but the time zone matters. I recommend converting all times to GMT/UTC within the DB.	[reply]


Think about Loose Coupling
	PerlMonks