> -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" (
> >
> 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 la
Jean-Michel POURE wrote:
>
> M$ Access2K relies on timestamps to update fields and 7.3 replaces timestamp
> -> timestamptz. Are there any timestamp in your table or only dates? Maybe
> you could copy table definition in your mail?
Here is an example of the table definition. I use the timestamptz
Le Jeudi 11 Avril 2002 13:19, noy a écrit :
> Then when I am trying to update this field from ACCESS I have an error and
> the entry can't be updated because the dates are not equals.
Dear Noy,
M$ Access2K relies on timestamps to update fields and 7.3 replaces timestamp
-> timestamptz. Are ther
Hi,
I having some problem with the date fields migration from 7.1.3 version to 7.2
version...
In my current version PostgreSQL 7.1.3 on i686-pc-linux-gnu, compiled by GCC
2.96 I get this result
select now();
now
2002-04-11 12:58:33+02
(1 row)
In
