> -----Original Message-----
> From: Jean-Michel POURE [mailto:[EMAIL PROTECTED]]
> Sent: 11 April 2002 15:10
> To: noy
> Cc: [EMAIL PROTECTED]
> 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 [EMAIL PROTECTED] would help.
Regards, Dave.
---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
