From: | Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> |
---|---|
To: | Popovics Attila <apopovics(at)interm(dot)gtk(dot)gau(dot)hu> |
Cc: | pgsql-odbc(at)postgresql(dot)org |
Subject: | Re: Read-only records with timestamp |
Date: | 2002-04-30 23:34:23 |
Message-ID: | 3CCF29FF.C37060D6@tpf.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
Popovics Attila wrote:
>
> Hi
> I have some tables with timestamp field
> (timestamp with time zone | default now()).
> It worked well in 7.1.3, but in 7.2.1 the newly inserted records are
> read only through the odbc (MS Access, pgAdmin 1.2.0).
> I analized the log files and I found that:
> on update or on delete the client sends string like this
> 'update .... set .... where ... and "idoppont" = '2002-04-26 14:05:17.44'::timestamp'
>
> but
>
> in plsql in same record
> the value of the field is 2002-04-26 14:05:17.440044+02
PostgreSQL's default timestamp is timestamp(6).
Access seems to handle timestamp up to timestamp(3)
though ODBC can handle up to timestamp(9).
Probably you have to use timestamp(n) (n<=3) instead
of default timestamp.
Hiroshi Inoue
http://w2422.nsk.ne.jp/~inoue/
From | Date | Subject | |
---|---|---|---|
Next Message | Hiroshi Inoue | 2002-04-30 23:36:43 | Re: ODBC Thread Safety |
Previous Message | Kevin Ormond | 2002-04-30 17:12:06 | ODBC Thread Safety |