* Max Nikulin <maniku...@gmail.com> [2023-01-15 08:05]: > I totally agree with the recommendation to use timestamptz for data related > to something in history: billing, bank transactions, etc. > > However it is call to trouble for planned events and schedules. Not > frequent, so almost untested use cases. > > If I remember correctly, another type, timestamp (without tz), may be cast > on demand to any timezone (stored in another column or passed from > application). So it may be used obtain correct UTC timestamp after update of > timezone database.
It is about representation. If time is represented as UTC, by user in Brazil, how is somebody in Russia going to understand when is the meeting? Call for trouble is when there is UTC time only as that requires users to calculate themselves the different time zone, instead, computer is for such calculations there. When time is specified with time zone, then user in any ther time zone can see that in his own time zone. In the context of Org files, that would mean that there must exist function which would convert time zone timestamps into local time zone for proper representation. Only with such functions problems are gone. Without such function to convert time zones in different time zone, user will see time zone from Brazil and will run into difficulties. -- Jean Take action in Free Software Foundation campaigns: https://www.fsf.org/campaigns In support of Richard M. Stallman https://stallmansupport.org/
