Re: Inserting Calendar.Time in a database

["Martin Dowie" <martin.dowie@btopenworld.com>]

Dmitry A. Kazakov wrote:
>> But even if it isn't atomic it's only going to be 'wrong' at most
>> twice a year and only for a second or so each time.
>
> Should we shut down the systems for that period of time? (:-)) Then
> one cannot deal with past and future times. The time zone itself is
> not constant. Governments are very inventive in making our life
> harder. Time stamps should be independent on this chaos.
>
> So I am not convinced that Ada.Calendar is a proper place for dealing
> with UTC. Time zones are OK there, no question. But similarity
> between zone times and UTC is rather apparent. As I said UTC is
> monotonic, so it should be Ada.Real_Time.

Or just read the UTC Offset until you get 2 values that are the same...