Re: Inserting Calendar.Time in a database

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

Dmitry A. Kazakov wrote:
> No. That would be just a stamp. A time stamp identifies the time of
> object creation. One more typical example: you measure some signal
> and wish to display it on-line as a wave form on the other side of
> the globe. Nether measurement points are equidistant, nor something
> concrete could be said about the communication channel.

Er, sorry, that's just not how the word "timestamp" is used either in
English
or in engineering (at least here in the UK) - it does not need to be tied to
UTC or local time or anything other than 'time from reset' (usually). So
long
as the period between 'ticks' is known then you have all the information you
need.

It may be that you need to synch several boards but all you need to do is
find
the relative differences between the different start points (i.e. where each
board thought '0' was).


> Ada.Real_Time is also about time. That you can view a clock reading as
> year, month, etc tells nothing about time. It tells only about the
> time base of the duration interval the clock return. The "system
> start" base is as good as any other.

...and that's exactly why you don't need UTC! :-)