Skip site navigation (1) Skip section navigation (2)

Re: Date representation

From: Dave Page <dpage(at)vale-housing(dot)co(dot)uk>
To: "'jm(dot)poure(at)freesurf(dot)fr'" <jm(dot)poure(at)freesurf(dot)fr>,noy <noyda(at)isoco(dot)com>
Cc: pgadmin-hackers(at)postgresql(dot)org
Subject: Re: Date representation
Date: 2002-04-11 14:33:46
Message-ID: FED2B709E3270E4B903EB0175A49BCB129337D@dogbert.vale-housing.co.uk (view raw or flat)
Thread:
Lists: pgadmin-hackers

> -----Original Message-----
> From: Jean-Michel POURE [mailto:jm(dot)poure(at)freesurf(dot)fr] 
> Sent: 11 April 2002 15:10
> To: noy
> Cc: pgadmin-hackers(at)postgresql(dot)org
> Subject: Re: [pgadmin-hackers] Date representation
> 
> 
> > CREATE TABLE "EMPLOYEE_SYSTEM" (
> >         "EMP_ID" integer,
> >         "EMP_EMAIL" character varying(80),
> >         "EMP_TIMESTAMP" timestamp with time zone,
> > );
> 
> Your schema is correct (timestamp with time zone = timestamptz).
> 
> > > By the way, did you upgrade pgAdmin2 and odbc driver to 
> the latest 
> > > version? Yes, I upgrade the driver version in windows.
> 
> Try Advanced options in ODBC and enable / disable fake index and row 
> versioning. Does it make it?
> 
> This problem is Access2K related: Access 2K need a timestamp 
> value to update 
> records. As far as I know, this used to be the case in 7.1...
> 
> Maybe something changed since 7.1. Any idea Dave?

I think it's a PostgreSQL thing, rather than Access or psqlODBC. Now() is
returning much higher precision in the seconds than previously. May be a
post to pgsql-general(at)postgresql(dot)org would help. 

Regards, Dave.

pgadmin-hackers by date

Next:From: Jean-Michel POUREDate: 2002-04-12 10:42:04
Subject: Various issues
Previous:From: Jean-Michel POUREDate: 2002-04-11 14:09:38
Subject: Re: Date representation

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group