Re: Insert statement changes timestamp value from MS Access - Mailing list pgsql-bugs

From Richard Huxton
Subject Re: Insert statement changes timestamp value from MS Access
Date
Msg-id 42E8F391.1060702@archonet.com
Whole thread Raw
In response to Re: Insert statement changes timestamp value from MS Access  ("David Dabney" <David.Dabney@noaa.gov>)
List pgsql-bugs
David Dabney wrote:
> The more I thought about this I realized it's not a bug and I'm sorry to
> have perstered the list.  The fact that the data logger was deployed
> before and after a time change and it was not setup to update itself
> created this problem.  I just have to push forward all the times after
> the change and then import the data.  We've been trying to get the
> scientists to use UTC.....maybe this will help them understand why they
> should be doing that.

The other thing you should do is use "timestamp with time zone" to store
your timestamps. Otherwise, you aren't storing an absolute time at all.

--
   Richard Huxton
   Archonet Ltd

pgsql-bugs by date:

Previous
From: "David Dabney"
Date:
Subject: Re: Insert statement changes timestamp value from MS Access
Next
From: Richard Huxton
Date:
Subject: Re: BUG #1795: mirroring