Jasen Betts wrote:
> On 2012-05-29, David Salisbury <salisbury@globe.gov> wrote:
>>
>> On 5/27/12 12:25 AM, Jasen Betts wrote:
>>> The query: "show integer_datetimes;" should return 'on' which means
>>> timestamps are microsecond precision if it returns 'off' your database
>>> was built with floating point timstamps and equality tests will be
>>> unreliable,
>> I find that rather interesting. I was told that I was losing microseconds
>> when I extracted an epoch from the difference between two timestamps and casted
>> that value to an integer. So if I have integer timestamps ( your case above )
>> I get microseconds, but integer epochs is without microseconds?
>
> yeah, the microseconds appear as fractions of seconds, so in the
> conversion to integer epoch they get rounded off.
I think you need to consider what you're actually computing and
measuring. My understanding is that Meeus's Equation of Time calculation
is good to something like 250mSec so that's the limit of your accuracy,
but as soon as you start taking refraction and atmospheric turbulence
into account- even with the Sun high above the horizon- you're going to
degrade that.
--
Mark Morgan Lloyd
markMLl .AT. telemetry.co .DOT. uk
[Opinions above are the author's, not those of his employers or colleagues]