On Monday 05 January 2009 5:29:19 am Jolles, Peter M (GE Infra, Energy) wrote:
> On Saturday, January 03, 2009 6:27 PM, David T Wilson wrote:
> > Those are the dates of daylight savings time kicking in-
> > which happens, not coincidentally, at 2am.
> >
> > What's the type of the field you're tryin
On Saturday, January 03, 2009 6:27 PM, David T Wilson wrote:
> Those are the dates of daylight savings time kicking in-
> which happens, not coincidentally, at 2am.
>
> What's the type of the field you're trying to import into,
> and how are you doing the import?
That makes a lot more sense n
Jolles, Peter M (GE Infra, Energy) wrote:
I am trying to migrate several years of historical data with timestamps
from an MS Access database to Postgres. I am running into an issue where
specific dates/times get pushed one hour ahead, which creates duplicate
date/time stamps or failes the import
On Sat, Jan 3, 2009 at 5:59 PM, Jolles, Peter M (GE Infra, Energy)
wrote:
> For example, on these days, 4/7/02 2:00 AM imports to 4/7/02 3:00 AM.
> 4/6/03 2:15 AM imports as 4/6/03 3:15 AM, etc. All other dates and times
> do not give any errors. I have tried to extract the date and create a
> t
I am trying to migrate several years of historical data with timestamps
from an MS Access database to Postgres. I am running into an issue where
specific dates/times get pushed one hour ahead, which creates duplicate
date/time stamps or failes the import if I have that defined as my
primary key. Th
