![]() Apparently not a lot of usability considerations went into this part of the SQL standard (or none of the big database vendors whose voice carries weight in the standard committee had a smarter implementation). Users or applications that have to cope with daylight savings time changes have to change the offset at the appropriate times to reflect that. ![]() In other words, the standard only has time zone management provisions for representing an offset from UTC. The time zone displacement is constant throughout a time zone, and changes at the beginning and end of Summer Time, where applicable. Local time is equal to UTC (Coordinated Universal Time) plus the time zone displacement, which is an interval value that ranges between INTERVAL ‘–14:00’ HOUR TO MINUTE and INTERVAL ‘+14:00’ HOUR TO MINUTE. The surface of the earth is divided into zones, called time zones, in which every correct clock tells the same time, known as local time. It has the following to say about time zones: The SQL standard has rather limited provisions for specifying time zones: So I thought it might be worth to write up an introduction to time zone management and recommendations for its practical use. ![]() In addition, PostgreSQL’s implementation of timestamp with time zone is somewhat surprising. Next to character encoding, time zones are among the least-loved topics in computing. Data type IANA postgresql timestamp timestamp with time zone timestamptz timezone ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |